Since 2024, dozens of local community-led protest campaigns have emerged in opposition to AI data centers. == Motivations == Organized opposition to AI data centers has been driven by concerns about energy use, energy costs, noise pollution, air pollution, and water waste. Opposition sentiment is widespread with a Gallup poll conducted in March 2026 showing that 70% of respondents oppose the construction of new AI data centers in their neighborhood. == Impact == In 2025, local opposition to AI data centers led to the delay or cancellation of projects totalling US$156 billion. == Specific protests and outcomes in the United States == According to Data Center Watch, there are has been a wave of dozens of protests against AI data centers since 2022. Below is a non-exhaustive list of some notable examples. === Goodyear and Buckeye, Arizona: Tract AI Data Center Proposal === In Goodyear and Buckeye, Arizona, a $14 billion project by developer Tract was withdrawn after local authorities blocked necessary rezoning in response to pressure from resident organizers. Opponest stiff resistance due to concerns over building heights, noise pollution, and the potential strain on local utilities. However, the company announced a revised project near the Buckeye airport in August 2024, with the backing of local officials and the mayor. === Peculiar, Missouri: Diode Ventures Harper Road Technology Park Proposal === In Peculiar, Missouri, residents from the group "Peaceful Peculiar" organized to stop a data center proposal from Diode Ventures called Harper Road Technology Park. Citing concerns around noise and light pollution, health, environmental impacts, jobs, property values, and energy use, organizers attended local planning and zoning meetings in large numbers and lobbied councilors to reject the proposal. Ultimately, the city council unanimously rejected the proposal in September 2024. === Chesterton, Indiana: Provident Realty Advisors Proposal === In Chesterton, Indiana, the Texas-based company Provident Reality Advisors applied for a $1.3 billion construction of a data center complex on the Brassie Golf Club property. Provident Realty Advisors wanted to purchase the 200 acres owned by PPM Chesterton LLC in 2024 order to build a data center complex, with eight buildings and an end user of a hyperscaler. The Town Council of Chesterton released a statement saying that they would never support this project, at least not at the scale and location it was planned for. They cited fears of added noise for locals, electrical or water management concerns, the intrusiveness of a data center built next to houses, and more. Provident released a statement shortly after rescinding their plan, because it was clear than the town of Chesterton would not support them. === Cascade Locks, Oregon: Roundhouse Digital Infrastructure Proposal === Startup data center developer Roundhouse Digital Infrastructure had planned to build out a 10-megawatt data center using a vacant industrial building and nearby 10-acre site in the Port of Cascade Locks, Oregon. After significant organized community opposition, the project was abandoned. === Forth Worth, Texas: WUSF 5 Rock Creek East Proposal === In September 2024, the City Council of Fort Worth, Texas approved a zoning change that would allow construction of a data center. In responses, neighbors mounted opposition citing concerns about traffic, light pollution, energy consumption, water use, and noise issues if the data center were to be built. In response to extensive public comments opposing a tax break for the data center, a city councilor withdrew his motion to approve the tax break. As of April, 2026, the future of the project is still uncertain. === Santa Clara, California: GI Partners Proposal === GI partners sought to build a new AI data center in Santa Clara, California, which is already home to many data centers, by acquiring a conditional permit use that would have allowed the developer to knock down a property and replace it with a data center. To obtain this permit they were required to go before members of the Planning Commission. Ultimately, the project was delayed with the Planning Commission requiring GI partners to do more public outreach. === Virginia === ==== Richmond: DC Blox Proposal ==== After residents organized to lobby the municipal government to block the proposal to avoid noise pollution and higher energy use, commissioners denied the company's permit. ==== Catlett Station: Headwaters Site Proposal ==== In Catlett, Virginia, developer Headwaters proposed construction of a data center complex just north of the town in 2020. In response, a residents' organization called "Protect Catlett" was formed to oppose the project. Arguments against the data center involved its impacts on water and power availability, its noise as a residential disturbance, and its destruction of historic and community heritage buildings. Arguments in favor cited job creation and $20 million in local tax revenue if the project were to go through. Protect Catlett utilized town halls and public comments to mobilize opposition to the project. They also dedicated time to educating other residents about the project's negative impacts and canvassing door-to-door in order to garner even more opposition to the project. Ultimately, after fervent opposition from most town residents, the project was canceled by the town and the developer. ==== Culpeper County: Culpeper Acquisitions Proposal ==== Culpeper Acquisitions, LLC, proposed a massive $12 billion data center project in Culpeper County, Virginia, designed to feature 4.6 million square feet of space across nine multi-story buildings. Coalition to Save Culpeper (C2SC) is an activist organization formed to resist the development of the project. C2SC has been active on many fronts including, messaging on social media, reaching out to local officials, and organizing meetings to bring community members with aligned interests together. Ultimately, the project was delayed due to unanimous denial by the Culpeper County Planning Commission on June 12, 2024, which was driven by intense opposition from C2SC. C2SC was successful in their mission largely because they were able to get so many people from the community behind it, and put enough pressure on local officials to take action. ==== Midlothian: Province Group Proposal ==== In late October 2025, the Powhatan County Board of Supervisors in Virginia voted unanimously to approve the $3 billion data center, despite the county's Planning Commission having unanimously recommended denial several days earlier. The reasoning behind their support for the center is that it will generate substantial tax revenue, reducing the county's reliance on residential property taxes. This appeal of lowering residential property taxes is the major selling point for the center's development. The developer, California-based Province Group, incentivized the Board by being agreeable to its conditions for building the center. The center is still on track for development, but faces local resistance, though little information is available on specific groups opposing it. ==== Warrenton: Amazon Proposal ==== Citizens for Farquier County (CFFC) advocates to "preserve the natural, historic and agricultural resources" of their county. Historically, this has meant opposing the building of a dam or lights in front of fast food stores. This group has recently mobilized in opposition of a plan to build data centers for Amazon. They first filed a suit to stop the construction in 2023 and it has been in litigation ever since. The case hinges on opposition to a 2021 zoning amendment which allowed data centers to be built in town. CFFC's lawyer, Dale Mullen, argues that this amendment violates state law, which requires such amendments to state their "public purpose". They argue that the permit for the Amazon data center was "void from the beginning". The CFFC also organized to vote out town council members who approved the first data center and were up for reelection, replacing them with candidates who opposed the data center. In May 2025, after attending town council meetings to speak out against the data center, the planning commission voted 4–1 to remove the zoning amendment allowing data center construction in town, citing public opposition. Currently, CFFC is advocating along with Piedmont Environmental Group, for phasing out data center tax breaks at the state level. ==== France: Marseille opposition ==== In France, local opposition materialised in response to proposed data centre developments, especially in and around the city of Marseille. Opposition came from activists, such as "Clouds Were Under Our Feet" group, residents ,and local politicians. Issues raised related to energy use, environmental impact, and limited local benefits (such as the creation of a few jobs only). == Legislation in the United States == Legal limits and moratoriums on the construction of new d
Database-as-IPC
In computer programming, Database-as-IPC may be considered an anti-pattern where a disk persisted table in a database is used as the message queue store for routine inter-process communication (IPC) or subscribed data processing. If database performance is of concern, alternatives include sockets, network socket, or message queue. British computer scientist, Junade Ali, defined the Database-as-IPC Anti-Pattern as using a database to "schedule jobs or queue up tasks to be completed", noting that this anti-pattern centres around using a database for temporary messages instead of persistent data. == Controversy == The issue arises if there is a performance issue, and if additional systems (and servers) can be justified. In terms of performance, recent advancements in database systems provide more efficient mechanisms for signaling and messaging, and database systems also support memory (non-persisted) tables. There are databases with built-in notification mechanisms, such as PostgreSQL, SQL Server, and Oracle. These mechanisms and future improvements of database systems can make queuing much more efficient and avoid the need to set up a separate signaling or messaging queue system along with the server and management overhead. While MySQL doesn't have direct support for notifications, some workarounds are possible. However, they would be seen as non-standard and therefore more difficult to maintain.
Qualification problem
In philosophy and AI (especially, knowledge-based systems), the qualification problem is concerned with the impossibility of listing all the preconditions required for a real-world action to have its intended effect. It might be posed as how to deal with the things that prevent me from achieving my intended result. It is strongly connected to, and opposite the ramification side of, the frame problem. John McCarthy gives the following motivating example, in which it is impossible to enumerate all the circumstances that may prevent a robot from performing its ordinary function: [T]he successful use of a boat to cross a river requires, if the boat is a rowboat, that the oars and rowlocks be present and unbroken, and that they fit each other. Many other qualifications can be added, making the rules for using a rowboat almost impossible to apply, and yet anyone will still be able to think of additional requirements not yet stated.
Journal of Experimental and Theoretical Artificial Intelligence
The Journal of Experimental and Theoretical Artificial Intelligence is a quarterly peer-reviewed scientific journal published by Taylor and Francis. It covers all aspects of artificial intelligence and was established in 1989. The editor-in-chief is Eric Dietrich (Binghamton University), the deputy editors-in-chief are Li Pheng Khoo (School of Mechanical & Aerospace Engineering, Nanyang Technological University) and Antonio Lieto (Department of Computer Science, University of Turin). == Abstracting and indexing == The journal is abstracted and indexed in: According to the Journal Citation Reports, the journal has a 2020/2021 impact factor of 2.340 .
National Library of Medicine classification
The National Library of Medicine (NLM) classification system is a library indexing system covering the fields of medicine and preclinical basic sciences. Operated and maintained by the U.S. National Library of Medicine, the NLM classification is patterned after the Library of Congress (LC) Classification system: alphabetical letters denote broad subject categories which are subdivided by numbers. For example, QW 279 would indicate a book on an aspect of microbiology or immunology. The one- or two-letter alphabetical codes in the NLM classification use a limited range of letters: only QS–QZ and W–WZ. This allows the NLM system to co-exist with the larger LC coding scheme as neither of these ranges are used in the LC system. There are, however, three pre-existing codes in the LC system which overlap with the NLM: Human Anatomy (QM), Microbiology (QR), and Medicine (R). To avoid further confusion, these three codes are not used in the NLM. The headings for the individual schedules (letters or letter pairs) are given in brief form (e.g., QW - Microbiology and Immunology; WG - Cardiovascular System) and together they provide an outline of the subjects covered by the NLM classification. Headings are interpreted broadly and include the physiological system, the specialties connected with them, the regions of the body chiefly concerned and subordinate related fields. The NLM system is hierarchical, and within each schedule, division by organ usually has priority. Each main schedule, as well as some sub-sections, begins with a group of form numbers ranging generally from 1–49 which classify materials by publication type, e.g., dictionaries, atlases, laboratory manuals, etc. The main schedules QS-QZ, W-WY, and WZ (excluding the range WZ 220–270) classify works published after 1913; the 19th century schedule is used for works published 1801–1913; and WZ 220-270 is used to provide century groupings for works published before 1801. == Classification categories == === Preclinical Sciences === QS Human Anatomy QT Physiology QU Biochemistry QV Pharmacology QW Microbiology & Immunology QX Parasitology QY Clinical Pathology QZ Pathology === Medicine and Related Subjects === W Health Professions WA Public Health WB Practice of Medicine WC Communicable Diseases WD Disorders of Systemic, Metabolic, or Environmental Origin, etc. WE Musculoskeletal System WF Respiratory System WG Cardiovascular System WH Hemic and Lymphatic Systems WI Digestive System WJ Urogenital System WK Endocrine System WL Nervous System WM Psychiatry WN Radiology. Diagnostic Imaging WO Surgery WP Gynecology WQ Obstetrics WR Dermatology WS Pediatrics WT Geriatrics. Chronic Disease WU Dentistry. Oral Surgery WV Otolaryngology WW Ophthalmology WX Hospitals & Other Health Facilities WY Nursing WZ History of Medicine 19th Century Schedule
Z-order
Z-order is an ordering of overlapping two-dimensional objects, such as windows in a stacking window manager, shapes in a vector graphics editor, or objects in a 3D application. One of the features of a typical GUI is that windows may overlap, so that one window hides part or all of another. When two windows overlap, their Z-order determines which one appears on top of the other. == Definition == The term "Z-order" refers to the order of objects along the Z-axis. In coordinate geometry, X typically refers to the horizontal axis (left to right), Y to the vertical axis (up and down), and Z refers to the axis perpendicular to the other two (forward or backward). One can think of the windows in a GUI as a series of planes parallel to the surface of the monitor. The windows are therefore stacked along the Z-axis, and the Z-order information thus specifies the front-to-back ordering of the windows on the screen. An analogy would be some sheets of paper scattered on top of a table, each sheet being a window, the table your computer screen, and the top sheet having the highest Z value. == Use == Typically, users of a GUI can affect the Z-order by selecting a window to be brought to the foreground (that is, "above" or "in front of" all the other windows). Some window managers allow interaction with windows while they are not in the foreground, while others will bring a window to the front whenever it receives input from the user. It is also possible for special windows to be designated "always on top"; these are then fixed to the top of the Z-order so that (with few exceptions) no other window can overlap them. When dealing with visual objects on a computer screen, an object with a Z-order of 1 would be visually "underneath" an object with a Z-order of 2 or greater. This is the same as making "layers" of objects where the Z-order determines what object is on top of another. An HTML page can use CSS to specify the Z-order so that some objects can be layered over others. Z-ordering is also used in 3D applications to determine object visibility based on overlap from other objects. This confers a speed advantage to the user as the computer does not need to render unseen objects. In practice, of course, some objects may be only partially obscured, and this is a complication that must be taken into account. In early real-time 3D graphics, Z-order was applied on a per-polygon basis to avoid using Z-buffer, which was considered expensive at the time. In modern 3D graphics, Z-order is used for order-dependent rendering, for example with semi-transparent objects. It can also be used to reduce the problem of Z-fighting, by either rendering farther objects first and then using weak inequality as the depth test or, conversely, rendering front-to-back and using strict inequality. == z-index == The actual number assigned to a particular place in the Z-order is sometimes known as the z-index. In particular the CSS property that sets the stack order of specific elements is known as the z-index. An element with greater stack order is always in front of another element with lower stack order. Negative values can also be used in the same manner. A negative value will appear behind a positive one. z-index only works on elements that have a position value (e.g. position: relative;) and for many coders, this one of the first things to investigate when debugging why the z-index isn't working. Like all other CSS properties, it can be set with JavaScript, with the following syntax:
Framework Convention on Artificial Intelligence
The Framework Convention on Artificial Intelligence and Human Rights, Democracy and the Rule of Law (also called Framework Convention on Artificial Intelligence or AI convention) is an international treaty on artificial intelligence. It was adopted under the auspices of the Council of Europe (CoE) and signed on 5 September 2024. The treaty aims to ensure that the development and use of AI technologies align with fundamental human rights, democratic values, and the rule of law, addressing risks such as misinformation, algorithmic discrimination, and threats to public institutions. More than 50 countries, including the EU member states, have endorsed the Framework Convention on Artificial Intelligence. == Background == The development of the Framework Convention on AI emerged in response to growing concerns over the ethical, legal, and societal impacts of artificial intelligence. The Council of Europe, which has historically played a key role in setting human rights standards across Europe, initiated discussions on AI governance in 2020, leading to the drafting of a binding legal framework. The process of creating the Framework Convention began in 2019 with the ad hoc Committee on Artificial Intelligence (CAHAI) assessing the feasibility of the instrument. In 2022, the Committee on Artificial Intelligence (CAI) took over the process, drafting and negotiating the text of the Convention. The treaty is designed to complement existing international human rights instruments, including the European Convention on Human Rights and the Convention for the Protection of Individuals with regard to Automatic Processing of Personal Data. == Structure and content == The Convention establishes fundamental principles for AI governance, including transparency, accountability, non-discrimination, and human rights protection through eight chapters and 26 articles. Adopted in 2024, this landmark treaty addresses AI governance through seven core principles and detailed implementation mechanisms. It mandates risk and impact assessments to mitigate potential harms and provides safeguards such as the right to challenge AI-driven decisions. It applies to public authorities and private entities acting on their behalf but excludes national security and defense activities. Implementation is overseen by a Conference of the Parties, ensuring compliance and international cooperation. Activities within the AI system lifecycle must adhere to seven fundamental principles, ensuring compliance with human rights, democracy, and the rule of law. The treaty also establishes remedies, procedural rights and safeguards, and risk and impact management requirements to promote accountability, transparency, and responsible AI development. The treaty consists of five chapters. Chapter I contains general provisions. Chapter II states the general obligation to protect human rights and the integrity of democratic processes and respect of the rule of law. The main principles and rights are contained in Chapter III, which consists of Articles 6 to 13. Chapter IV (Articles 14 to 15) sets up the legal remedies. Chapter V states the risk and impact management framework. Chapter VI facilitates the implementation criteria of the treaty. Chapter VII sets the co-operation and oversight mechanisms. Chapter VIII contains various concluding clauses. Article 1 declares the objectives of the treaty, to ensure that activities within the lifecycle of artificial intelligence systems are fully consistent with human rights, democracy and the rule of law. == Entry into force == The treaty will enter into force on the first day of the month following the expiration of a period of three months after the date on which five ratification made by five countries, including three member states of the Council of Europe. == Competing approaches == While the CoE's AI Convention represents a multilateral effort to regulate AI through a human rights-based approach, alternative frameworks have also been proposed. One notable example is the Munich Draft for a Convention on AI, Data and Human Rights, an initiative led by legal scholars and policymakers in Germany. The Munich Draft advocates for stronger safeguards against AI-related risks, emphasizing stricter data protection measures, accountability for AI developers, and explicit prohibitions on high-risk AI applications, such as mass surveillance and autonomous lethal weapons. Unlike the CoE convention, which focuses on balancing innovation with regulation, the Munich Draft takes a more precautionary stance, calling for tighter controls over AI deployment in sensitive domains. Other competing international efforts include the OECD’s AI Principles, the GPAI (Global Partnership on AI), and the European Union's AI Act, each of which offers different regulatory strategies to govern AI at regional and global levels. == Signatories == Signatories include Andorra, Canada, the European Union, Georgia, Iceland, Israel, Japan, Liechtenstein, the Republic of Moldova, Montenegro, Norway, San Marino, Switzerland, Ukraine, the United Kingdom, the United States, and Uruguay. == Endorsement == The treaty was widely endorsed by leading AI policy experts, including Stuart J. Russell, Virginia Dignum, Emma Ruttkamp-Bloem, Pascal Pichonnaz, Maria Helen Murphy, Angella Ndaka, Hannes Werthner, Katja Langenbucher, Gry Hasselbalch, Ricardo Baeza-Yates, Kutoma Wakunuma, Gianclaudio Malgieri, Oreste Pollicino, Nagla Rizk, Giovanni Sartor, Lee Tiedrich, Ingrid Schneider, Eduardo Bertoni, Garry Kasparov, Merve Hikcok, and Marc Rotenberg. The treaty was also endorsed by notable political leaders, including Theodoros Roussopoulos, President of the Parliamentart Assembly in the Council of Europe, and Christopher Holmes, Member of the House of Lords of the United Kingdom, and by the International Bar Association (IBA), and personally by Almudena Arpón de Mendívil, President of the IBA. The Center for AI and Digital Policy (CAIDP) has been carrying out a campaign to promote endorsement of the treaty by urging various countries to sign and ratify the treaty. The CAIDP further urged the countries to make a clear and firm commitment to ensure the full inclusion of the private sector under the treaty’s provisions.