DEV Community: SnackIQ

How AI Actually Steals Your Attention

SnackIQ — Fri, 29 May 2026 08:01:50 +0000

AI recommendation systems are deliberately engineered to steal your attention — and they're extraordinarily good at it. Every scroll, pause, and replay you make is fed into models that learn exactly what keeps you locked to a screen. Meta's internal researchers, in documents that became public during the 2021 Congressional hearings, acknowledged that their algorithms actively exploited psychological vulnerabilities to maximise time-on-platform. This isn't an accident or a side effect. It's the product. The average person now touches their phone over 2,600 times per day, according to research by Dscout, a mobile research firm. AI systems aren't just showing you content — they're constructing a real-time psychological profile and using it to override your intentions. Understanding the mechanism changes how you see every feed you scroll.

What does an AI recommendation engine actually do?

Most people imagine a recommendation algorithm as a fancy search engine — you like dogs, it shows you dogs. The reality is far stranger and more powerful than that.

At its core, a recommendation engine is a prediction machine. It doesn't just track what you like. It models what you're likely to engage with next, based on millions of behavioural signals: how long you hovered over a video before skipping, whether you watched a clip to 80% or 100%, which posts made you stop mid-scroll, and what time of day your resistance is lowest. Netflix has stated publicly that it analyses viewer behaviour across more than 200 million accounts to fine-tune its recommendations. YouTube processes over 80 billion data points per day to serve its next-video suggestions.

The model being optimised isn't 'show them things they enjoy.' It's 'maximise predicted watch time' — a subtly different goal with enormous consequences. Content that provokes anxiety, outrage, or compulsive curiosity tends to generate more engagement than content that leaves you feeling satisfied and done. A satisfied viewer closes the app. An anxious or intrigued one keeps scrolling.

These systems use a class of machine learning called collaborative filtering combined with deep neural networks. Collaborative filtering finds users who behave like you and maps their future behaviour onto your predictions. Deep networks layer in content features — audio, visual cues, text sentiment — to build a complete picture of what will hook you specifically. The result isn't personalisation in the warm sense of the word. It's precision targeting of your psychological weak points.

Why does AI target your brain's reward system?

The short answer: because it works, and your brain didn't evolve to resist it.

Dopamine is your brain's 'pursue this' signal — not a pleasure chemical, but an anticipation chemical. It fires hardest not when you get a reward, but when a reward is possible but uncertain. Slot machines exploit this. So do recommendation algorithms. The scroll feed is deliberately designed as a variable reward schedule — the same mechanism B.F. Skinner identified in the 1950s as the most potent form of behavioural conditioning. Most posts are mediocre. Occasionally you hit something brilliant. That unpredictability is the hook.

Tristan Harris, a former design ethicist at Google who later co-founded the Center for Humane Technology, testified before the US Senate in 2019 that tech companies had essentially built 'a race to the bottom of the brain stem' — competing to access the most primitive, least rational parts of human psychology. The AI isn't evil. It's just optimising for the metric it was given, and that metric is time-on-screen.

Research published in journals focused on behavioural psychology has found that intermittent reinforcement produces stronger habit loops than consistent rewards — and that these loops persist long after the rewarding content stops appearing. This is why you keep refreshing a feed even when nothing interesting is there. Your brain has been conditioned to expect the occasional hit, so it keeps pulling the lever.

The biological vulnerability here is deep. Humans evolved in environments where novel stimuli could mean food, danger, or opportunity. Ignoring novelty carried survival costs. AI systems have found a way to flood that ancient circuit with synthetic novelty at industrial scale.

How does AI learn to predict your weak moments?

The sophistication of modern recommendation systems goes far beyond what most people suspect. These models don't just learn your content preferences — they learn your psychological state across time.

Time-of-day patterns are among the most powerful signals. Research into digital behaviour consistently shows that people's resistance to distraction drops sharply in the evening and spikes mid-morning. Algorithms learn your personal version of this curve. If you're reliably vulnerable to autoplay at 10pm, the system will serve its most compelling content at that moment — not because a human made that decision, but because the model discovered the pattern in your data and exploited it automatically.

Emotional state inference is increasingly part of these systems too. Studies using smartphone sensor data have shown that typing speed, error rate, and scrolling velocity all correlate with mood and cognitive load. Some platforms have experimented with sentiment detection to assess whether a user is in a low-resistance emotional state. A 2014 experiment by Facebook, published in the Proceedings of the National Academy of Sciences, demonstrated that the platform could alter users' emotional states by manipulating their feeds — a finding that caused significant controversy but confirmed the directional capability.

Your social graph adds another layer. The AI doesn't just study you. It studies who you follow, who they engage with, and how information spreads through your network. Content that generates replies and shares produces a social proof signal the algorithm weaponises — showing you posts that already triggered emotional reactions in people like you, because emotional reactions are engagement, and engagement is the goal.

Does AI-driven attention capture actually harm you?

This is where the evidence becomes genuinely contested — but also genuinely worrying.

The most rigorous independent research suggests real costs. A large-scale study by researchers at Oxford University's Internet Institute, analysing data from over 350,000 adolescents across multiple countries, found associations between heavy social media use and lower wellbeing — particularly in girls and younger adolescents. Crucially, the effect was small in absolute terms, roughly comparable to the negative effect of wearing glasses on wellbeing (a comparison the researchers themselves made to contextualise the data), but consistent across multiple datasets.

For adults, attention fragmentation is the better-documented harm. Research from Microsoft and independently from the University of California found that the average knowledge worker takes over 20 minutes to return to a deep task after an interruption. AI-powered notifications are specifically designed to interrupt at moments of maximum susceptibility — which means the cost isn't one 20-minute recovery, it's dozens per day.

There's also the filter bubble effect: recommendation systems progressively narrow the information you see to match your existing beliefs and preferences, because agreeable content generates more engagement than challenging content. This has measurable downstream effects on political polarisation, according to researchers at institutions including MIT's Media Lab and NYU's Center for Social Media and Politics.

The counter-argument holds that correlation doesn't equal causation — people who are already anxious or lonely may use social media more, rather than social media making them anxious. That's fair. But the design intent of these systems — as revealed by internal documents from Meta and testimony from former Google and Twitter engineers — was never your wellbeing. It was your time.

Can you actually fight back against the algorithm?

Yes — but only if you understand what you're fighting.

The algorithm's power comes from prediction accuracy. The more data it has on you, the better it predicts your behaviour. The strategic response is to degrade that accuracy deliberately. This doesn't mean deleting your accounts (though that's the nuclear option). It means introducing noise into your behavioural signal.

Here are concrete approaches that disrupt algorithmic profiling:

Use chronological feeds wherever available. Twitter/X, Instagram, and Facebook all offer them. Chronological feeds bypass the recommendation layer entirely.
Consume content in batches, not streams. Binge-then-stop beats constant low-level exposure. Your total time may be the same, but the habit loop is harder to form without the variable reward structure.
Deliberately engage with content you're indifferent to. Liking or watching things that don't excite you confuses the model and reduces its precision.
Use browser extensions that remove recommendation feeds. Tools like DF YouTube strip the sidebar and autoplay queue, leaving search and subscriptions intact without the algorithmic layer.
Schedule your phone use. If the algorithm knows when you're vulnerable, scheduling removes that knowledge. Consistent 30-minute windows at set times break the pattern the model depends on.

The deeper point is this: you cannot outscroll an algorithm. Willpower is finite. The model is not. Every decision to engage trains the model further. The only durable response is structural — changing your environment and your inputs, not relying on discipline in the moment.

AI recommendation systems are among the most sophisticated behavioural engineering tools ever built — and most people interact with them dozens of times a day without knowing how they work. The mechanism isn't mysterious: exploit the dopamine circuit, learn your weak moments, serve precisely calibrated content at exactly the right instant. Once you see the machinery, every feed looks different. That's not paranoia. It's just understanding what the product actually is — and realising you're not the customer. You're the inventory.

Originally published on SnackIQ

AI Water Usage Reality Actually Debunked

SnackIQ — Tue, 26 May 2026 14:03:19 +0000

The ai water usage reality debunked comes down to one awkward fact: the numbers being shared online are technically true and wildly misleading at the same time. Yes, Microsoft reported that its global data center water consumption increased by roughly 34% between 2021 and 2022, coinciding with heavy AI infrastructure buildout. But when you divide that water across billions of queries, the per-interaction figure shrinks to a few millilitres — less than a sip of coffee. The viral headlines grabbed the big number and dropped the denominator. That's not journalism. That's a magic trick.

Where Did the 'AI Drinks Oceans' Claim Come From?

It started with a real paper. Researchers at UC Riverside and the University of Texas Arlington published work in 2023 estimating that a conversation of roughly 20 to 50 questions with ChatGPT could consume around 500 millilitres of water — about the volume of a standard plastic bottle. That number spread everywhere. Tech journalists ran it. Environmentalists shared it. The phrase 'AI is thirsty' became a minor cultural meme.

What the headlines almost never included was the context. That 500ml figure was an upper-bound estimate that accounted for both direct water use at the data center and the indirect water consumed upstream in generating the electricity powering the servers. Strip out the indirect portion — which follows the same accounting logic you'd apply to charging your phone or running your dishwasher — and the direct figure drops dramatically.

The researchers themselves were careful in their paper to note the significant uncertainty in these estimates. Water usage varies enormously depending on the season, the region, the cooling technology used, and whether a data center relies on air cooling, water cooling, or a hybrid approach. A facility in Iceland running on geothermal power has a completely different water profile than one in Arizona using evaporative cooling in summer heat.

The original research was solid. The amplification was not. That distinction matters, because treating a nuanced engineering estimate as a simple shocking statistic is exactly how misinformation about complex systems spreads.

What AI Actually Does to Water — The Real Mechanism

To understand the real footprint, you need to know how data centers actually use water. Most large facilities use one of two cooling approaches, and they have very different water profiles.

Air cooling uses fans and heat exchangers to dissipate heat. Water consumption is minimal or zero.- Evaporative cooling (cooling towers) works like a giant swamp cooler — water evaporates and carries heat away. This does consume meaningful amounts of water.- Hybrid systems switch between modes depending on ambient temperature, using water cooling only when outdoor air isn't sufficient to do the job.

Google, Microsoft, and Amazon all operate a global mix of these systems. In cooler climates — the Pacific Northwest, Scandinavia, Ireland — many facilities run on air cooling year-round. The water-intensive facilities tend to cluster in hot, dry regions where evaporative cooling is most effective: Arizona, Nevada, central Virginia in summer.

This geography matters. A ChatGPT query routed through a server in Dublin uses fundamentally different infrastructure than one hitting a data center in Phoenix in August. There is no single AI water figure — there's a range that spans an order of magnitude depending on where and when the computation happens.

Researchers studying data center efficiency have noted that the industry has made significant gains in Power Usage Effectiveness (PUE) over the past decade, and Water Usage Effectiveness (WUE) has followed a similar improvement trajectory at leading operators. The hyperscalers — Google, Microsoft, Amazon — publish annual sustainability reports tracking these metrics. The trend is toward less water per unit of computation, not more.

Is the Concern Completely Unfounded?

No — and this is where honest debunking gets complicated. The concern isn't fabricated. It's just mislocated.

The genuine issue isn't the water per query. It's geographic concentration. When a hyperscaler builds a 100-megawatt data center in a drought-stressed region — say, the American Southwest or parts of the Middle East — it draws on local water supplies that are already under pressure. A 2023 investigative report by the Associated Press documented residents and officials in places like Mesa, Arizona and rural Virginia expressing real concern about data center water permits competing with agricultural and residential needs.

This is a legitimate land-use and resource-allocation story. A large data center in a water-scarce area can draw millions of gallons per day from an aquifer that took centuries to fill. The fact that this equals only a millilitre per query doesn't help the farmer twenty miles away.

But notice what this version of the problem actually is: it's a zoning and permitting issue, not a reason to stop using AI. The same logic applies to semiconductor fabs, steel mills, paper plants, and bottled water facilities — all of which have faced identical local water conflicts. Calling it an 'AI water crisis' rather than a 'data center siting crisis' or an 'industrial water management failure' shapes the conversation in a way that generates outrage but points away from the actual lever: planning policy.

The town of Covington, Kentucky published analysis in 2025 showing that a proposed EV battery factory would use comparable amounts of water to a data center of similar scale. Nobody ran headlines saying electric cars are destroying water supplies.

How AI Water Use Compares to Things You Already Accept

Context is the thing viral statistics almost always destroy. So here's some.

A single almond requires approximately 12 litres of water to produce, according to data from the Pacific Institute. A 200ml glass of cow's milk takes around 120 litres. A cotton T-shirt takes roughly 2,700 litres from field to shelf. Meanwhile, a 20-question AI conversation uses somewhere between 0.003 and 0.5 litres depending on model, infrastructure, and methodology — a range that even at its upper end sits below a single almond.

The comparison isn't meant to dismiss environmental scrutiny of AI. It's meant to calibrate it. We have accepted enormous embedded water costs in food and clothing without thinking twice, while the AI figure — which is orders of magnitude smaller and actively shrinking as hardware efficiency improves — became a symbol of technological excess.

Part of what's happening is a phenomenon well-documented in environmental communication: tangible, nameable culprits attract more outrage than diffuse systemic ones. AI is a perfect villain because it's new, powerful, associated with wealthy corporations, and slightly mysterious. Agriculture uses roughly 70% of global freshwater withdrawals according to the UN Food and Agriculture Organization. That's not a secret. It just doesn't generate the same emotional charge as 'ChatGPT drinks a bottle of water every time you ask it a question.'

None of this means AI companies deserve a free pass on water reporting. Transparency matters. But proportionality matters too.

What the Evidence Actually Settles

The honest verdict on AI water usage lands somewhere most people find unsatisfying: it's real, it's manageable, and it's being eclipsed by a better story.

AI data centers do consume water. That consumption is growing as AI workloads expand. In specific localities with stressed water systems, new data center development deserves serious scrutiny and robust permitting requirements. These are valid concerns.

But the framing of 'AI is a water crisis' fails on the evidence. Per-query water use is small and shrinking as cooling technology improves. Total sector consumption, even under aggressive growth projections, represents a fraction of agricultural or manufacturing water demand. The viral statistics were technically derived from real research but stripped of the context that makes them meaningful.

The researchers who produced the original estimates have generally been careful to say their numbers should inform policy and design decisions — not personal guilt about using a chatbot. The gap between what the science said and what the headlines reported is itself a data point about how environmental communication goes wrong.

If you care about water — and you should, it's genuinely under pressure globally — the levers worth pulling are:

Supporting stronger water impact assessments for all industrial developments, not just AI- Advocating for data center siting rules that factor in regional water stress- Pressuring tech companies to publish WUE metrics and commit to closed-loop cooling where feasible

Skipping your ChatGPT query to save water? The evidence says that's not where the math works out.

The ai water usage reality debunked isn't a defence of big tech — it's a defence of proportional thinking. Real environmental problems deserve accurate framing. When AI gets cast as the villain in a crisis better explained by industrial siting policy, agricultural water use, and climate-driven drought, it crowds out the conversations that actually lead somewhere. The water is real. The scale, in context, is not what the headlines suggest. Knowing the difference is how you think clearly about technology — and everything else.

Originally published on SnackIQ

AI vs Industry: Who Really Wastes Water?

SnackIQ — Mon, 25 May 2026 08:03:42 +0000

AI water consumption compared to other industries tells a very different story than the headlines suggest. Yes, a large data center can consume up to 5 million gallons of water per day — enough to supply a town of 50,000 people, according to the Environmental and Energy Study Institute. That sounds alarming. But global agriculture accounts for roughly 70% of all freshwater withdrawals worldwide, according to the United Nations Food and Agriculture Organization. Steel production requires around 300 litres of water per tonne. A single kilogram of beef needs approximately 15,000 litres. Before writing off AI as a water catastrophe, it's worth actually running the comparison — because the numbers reveal something most coverage misses entirely.

How Much Water Does a Data Center Actually Use?

The cooling problem is real. Servers generate enormous heat, and that heat has to go somewhere. Most large data centers use evaporative cooling towers — essentially industrial-scale swamp coolers — that evaporate water to dissipate heat. This is where the water consumption happens, and it scales directly with the computational load inside.

The Environmental and Energy Study Institute reports that large data centers can consume up to 5 million gallons per day. That's the headline figure that circulates in worried news coverage. A mid-sized facility — think a campus-scale operation rather than a hyperscale cloud hub — consumes water comparable to a small hospital or a mid-sized hotel.

AI workloads make this worse. Training a large language model requires extended periods of intensive computation, which generates more heat than routine web serving or data storage. A single large training run can consume hundreds of thousands of litres of water. Inference — actually running AI queries after training — consumes less per interaction but adds up across billions of daily requests.

But here's the number that reframes everything: all data centers globally, AI-related and otherwise, account for roughly 0.2% of global freshwater withdrawals, based on estimates from water researchers tracking digital infrastructure. That's the entire sector — email, streaming, cloud storage, social media, and AI combined. It's not nothing. But it's a useful denominator.

Facility Type	Estimated Daily Water Use	Equivalent Comparison
Large hyperscale data center	Up to 5 million gallons	Town of 10,000–50,000 people
Mid-sized data center	~300,000–500,000 gallons	Large hotel or hospital
Small edge data center	~10,000–50,000 gallons	Large office building
All global data centers combined	~1–2 billion gallons	~0.2% of global freshwater withdrawals

The scale matters. A single facility sounds enormous. The global sector share sounds manageable. Both figures are accurate — which one you lead with determines the entire narrative.

How AI's Water Use Stacks Up Against Other Industries

Agriculture is the honest benchmark. The UN Food and Agriculture Organization consistently estimates that farming accounts for approximately 70% of global freshwater withdrawals. That's not a rounding error — it's the dominant human use of water on Earth, full stop. Growing one kilogram of rice requires roughly 3,500 litres. One kilogram of beef, around 15,000 litres. Cotton for a single T-shirt uses approximately 2,700 litres.

Heavy industry is also a major consumer. Steel production requires around 300 litres per tonne of steel at the efficient end, but older processes can use dramatically more. Semiconductor manufacturing — the industry that makes the chips inside every AI data center — is itself extraordinarily water-intensive, with some chip fabs using tens of millions of gallons per day. The irony is notable: reducing AI's water footprint requires better chips, but making those chips requires enormous quantities of water.

Fast fashion is another instructive comparison. Studies by environmental researchers estimate the global textile industry consumes roughly 93 billion cubic metres of water annually — enough to meet the needs of five million people. That's a sector that generates discretionary products, not the infrastructure of a global economy.

Industry / Activity	Water Consumption	Unit
Global agriculture	~70% of freshwater withdrawals	Annual global share
1 kg of beef	~15,000 litres	Per unit produced
1 kg of cotton (one T-shirt)	~2,700 litres	Per unit produced
Steel production	~300+ litres	Per tonne
Semiconductor fab (chip factory)	Tens of millions of gallons	Per day
All AI data centers globally	~0.2% of freshwater withdrawals	Annual global share

None of this excuses waste. But context determines whether a problem is urgent or catastrophic — and in this case, the comparison argues strongly for proportionality.

Where the Real Risk Actually Lives

The global percentage figure obscures a genuinely serious local problem. Data centers don't distribute their water demand evenly across the planet — they concentrate it. A hyperscale campus in a water-stressed region like the American Southwest, the Middle East, or parts of Southeast Asia draws from aquifers and river systems that may already be under severe pressure.

Virginia's Loudoun County — sometimes called the "Data Center Alley" of the world — hosts more data center capacity than almost anywhere else on Earth. These facilities sit in a relatively water-abundant region. But when Microsoft, Google, and Meta have built major campuses in Arizona or in Chile's Atacama-adjacent regions, the local water calculus looks entirely different. A global share of 0.2% becomes irrelevant when a specific aquifer services a specific community.

The Lincoln Institute of Land Policy has highlighted this location problem directly: the issue isn't just how much water AI uses globally, but where that water comes from. A data center in the rainy Pacific Northwest has a fundamentally different impact than the same facility in Phoenix. Critics arguing AI is a water crisis are often making a location argument, not a volume argument — and that's a more defensible position.

Data Center Location Type	Water Stress Risk	Local Impact Severity
Pacific Northwest (US)	Low — high rainfall, river access	Minimal under normal conditions
Northern Europe (Ireland, Sweden)	Very low — temperate climate	Minimal; ambient air cooling viable
Virginia / Mid-Atlantic (US)	Moderate — seasonal variation	Manageable with planning
Arizona / Nevada (US)	High — chronic drought conditions	Significant local competition with agriculture and residents
Middle East / North Africa	Very high — extreme water scarcity	Severe; desalination often required

This reframes the entire debate. The question isn't "does AI use a lot of water globally?" — it's "is AI competing for scarce water in places that can't afford the competition?"

Is the Tech Industry Actually Getting More Efficient?

The honest answer is: yes, but not fast enough to offset growth. Tech companies have invested heavily in water efficiency metrics, primarily through a measure called Water Usage Effectiveness (WUE) — the ratio of water used to the energy consumed by IT equipment. Lower WUE means more efficient cooling per unit of computation.

Google has reported WUE figures below 1.0 litre per kilowatt-hour at some of its most advanced facilities — well below the industry average. Microsoft has publicly committed to being water positive by 2030, meaning it aims to replenish more water than it consumes. Meta has similar pledges. These aren't purely performative: direct-to-chip liquid cooling and immersion cooling — where servers are submerged in non-conductive fluid — can dramatically reduce or eliminate the evaporative water loss that accounts for most consumption.

New cooling technologies are moving fast:

Direct-to-chip cooling circulates liquid coolant directly over processor chips, eliminating the need for large evaporative towers entirely.
Immersion cooling submerges hardware in dielectric fluid, achieving near-zero water evaporation with exceptional heat transfer.
Air-side economizers use outside air when temperatures allow, reducing water consumption during cooler months.
Closed-loop cooling systems recirculate water rather than evaporating it, dramatically cutting consumption per megawatt of compute.

The problem is that absolute water use is still rising because the industry is growing so fast that efficiency gains don't keep pace with new capacity. Efficiency per unit improves; total consumption still climbs. This is the same dynamic seen in automobile fuel efficiency over the past 30 years — cars got cleaner, but people bought more and bigger ones.

Cooling Technology	Relative Water Use	Adoption Status
Traditional air cooling (evaporative towers)	High (baseline)	Dominant, legacy facilities
Air-side economizers	Medium (seasonal benefit)	Widely deployed in cool climates
Direct-to-chip liquid cooling	Low	Growing rapidly in new builds
Immersion cooling	Near zero evaporative loss	Early adoption, high-performance clusters

What a Fair Verdict Actually Looks Like

Proportionality isn't absolution. AI does use water — meaningfully, measurably, and in ways that deserve scrutiny. The EESI is right that data center developers are tapping freshwater resources that communities depend on. The Lincoln Institute is right that location matters enormously. And the rapid expansion of AI infrastructure means that a currently modest global share could grow substantially over the next decade if the industry doesn't manage its footprint.

But the framing that AI is uniquely or catastrophically water-hungry doesn't hold up against the data. A cotton T-shirt uses more water than roughly 1,500 ChatGPT conversations. A single kilogram of beef uses more water than a data center running for several hours. The industries generating the most severe freshwater stress globally — agriculture, mining, heavy manufacturing — dwarf the tech sector by every measure.

The productive question isn't "is AI a water villain?" but rather: should AI data centers be built in water-stressed regions, and do local communities have adequate say? That's a governance and planning question, not a technology indictment.

Activity	Approximate Water Use	Context
1 ChatGPT query (estimated)	~0.5 litres	Per interaction, including training amortisation
1 kg of beef	~15,000 litres	30,000x a single AI query
1 cotton T-shirt	~2,700 litres	Equivalent to ~5,400 AI queries
10-minute shower	~60–80 litres	120–160x a single AI query
Washing a car	~150–200 litres	300–400x a single AI query
Global AI data centers annually	~0.2% of freshwater withdrawals	vs. agriculture at ~70%

The numbers don't exonerate the industry — they redirect the conversation toward where real leverage exists: smarter siting decisions, mandatory water disclosure, and faster adoption of waterless cooling technologies. That's a more useful argument than treating every ChatGPT query like a drought.

AI's water footprint is real, growing, and worth regulating — especially in drought-prone regions where data centers compete directly with farms and residents. But the comparison data is clear: agriculture, heavy manufacturing, and fast fashion consume water at a scale that makes the entire global data center sector look modest. The honest case against AI's environmental impact isn't that it's the biggest water consumer. It's that it's an avoidable one — and that the industry has the technology and resources to do far better than it currently does.

Originally published on SnackIQ

How AI Secretly Learns From Your Data

SnackIQ — Sat, 23 May 2026 14:04:12 +0000

How AI learns from user data isn't a mystery locked inside a server room — it's happening every time you click, skip, type, or correct a suggestion. A 2023 Stanford HAI report estimated that the largest AI models are now trained on datasets exceeding one trillion words of human-generated text, much of it scraped from the open web where you've left a trail. But the initial training is just the start. Every thumbs-down on a Spotify track, every rephrased search query, every time you tell a chatbot 'that's wrong' — all of it feeds back into the system. AI doesn't just learn once. It learns continuously, quietly, from the texture of your daily digital life.

What does 'learning' actually mean for an AI?

Most people picture AI learning the way humans do — absorbing knowledge, forming memories, having realisations. The reality is both simpler and stranger.

Machine learning is fundamentally a mathematical optimisation process. You give a system a massive dataset, define what a 'correct' answer looks like, and then let it adjust millions or billions of internal numerical settings — called parameters or weights — until its outputs match the desired answers as closely as possible. It's less like studying for an exam and more like tuning an enormous equaliser until the music sounds right.

There are three main approaches this takes:

Supervised learning — the model is trained on labelled examples. An email spam filter learns from millions of emails already tagged 'spam' or 'not spam' by humans.- Unsupervised learning — the model finds patterns on its own, without labels. Spotify's 'Discover Weekly' clusters listeners with similar taste without anyone defining what 'similar' means.- Reinforcement learning — the model experiments and receives reward signals. Chess-playing AI systems like DeepMind's AlphaZero used this to become superhuman in 24 hours of self-play, never once looking at historical human games.

What makes modern AI different from older software isn't that it follows rules. It's that it infers rules from examples. Feed it enough pictures of cats and it builds its own internal definition of 'cat' — one nobody explicitly programmed. That definition lives distributed across billions of numerical weights, invisible and unreadable even to the engineers who built the system.

Where does your personal data actually go?

Here's where it gets personal. The data AI systems train on isn't abstract — it's text you wrote, images you uploaded, searches you typed, and behaviours you exhibited without thinking.

When OpenAI trained GPT models, the training corpus included Common Crawl (a snapshot of hundreds of billions of web pages), digitised books, Wikipedia, and code repositories like GitHub. Researchers at the University of Washington have shown that language models can sometimes reproduce near-verbatim text from their training data when prompted correctly — meaning fragments of publicly posted personal blogs, forum posts, and social media updates are potentially encoded inside these systems.

But the more direct pipeline is feedback data. When you use a product like ChatGPT and rate a response, that signal is gold. OpenAI's RLHF process — Reinforcement Learning from Human Feedback — works precisely this way: human raters compare model outputs, and the model is updated to produce responses more like the preferred ones. Your 'thumbs down' is a training signal.

Google's search suggestions update based on aggregate query patterns across billions of users. Netflix's recommendation engine — which the company has publicly stated influences over 80% of content watched on the platform — retrains on viewing behaviour constantly. Even your hesitation matters: research on recommendation systems has found that dwell time (how long you linger on a page before clicking back) is treated as an implicit negative signal, meaning the system learns from what you almost clicked as much as what you did.

The uncomfortable truth is that 'your data' and 'anonymous aggregate data' blur together at scale. When a billion people's behaviours shape a model, the model reflects all of them — including you.

Why does AI keep learning after it's been built?

There's a widespread assumption that AI models are trained once and then deployed — like a textbook that gets printed and doesn't change. That's increasingly wrong.

Continuous learning — sometimes called online learning or fine-tuning — allows models to update on new data without being fully retrained from scratch. This is computationally cheaper and keeps systems current. TikTok's recommendation engine is the most cited example of this in action: it updates its model of your preferences within the first 30 minutes of use, notoriously accurate at mapping what keeps you watching before you've consciously understood your own preferences.

There are legitimate reasons for this. The world changes. Slang evolves. New products launch. Political events shift what's relevant. A model frozen in time goes stale fast — in AI research this is called concept drift, and it's a genuine engineering problem.

But continuous learning from user data creates its own risks. In 2016, Microsoft launched a Twitter chatbot called Tay that was designed to learn conversational patterns from user interactions in real time. Within 16 hours, coordinated users had trained it to produce racist and inflammatory content. Microsoft pulled it offline. The Tay incident became a landmark case study in why unfiltered real-time learning from user data needs guardrails.

Modern systems balance this with curated feedback loops: user signals are collected, filtered for spam and adversarial input, aggregated, and used in periodic fine-tuning runs rather than instantaneous updates. The feedback you give still matters — but it goes through a cleaner pipeline before it changes anything.

Can AI learn wrong things from your behaviour?

Yes. And this is one of the most actively researched problems in the field.

When AI learns from human behaviour, it learns human patterns — including human biases. Algorithmic bias is the term for when a model reproduces or amplifies unfair patterns baked into training data. Amazon's internal recruiting tool, trialled in the late 2010s, reportedly downgraded CVs that included the word 'women's' because it had trained on a decade of historical hiring decisions skewed toward male candidates. Amazon scrapped it.

Facial recognition systems trained predominantly on lighter-skinned faces have been shown by MIT Media Lab researcher Joy Buolamwini to perform significantly worse on darker-skinned women — error rates differing by more than 30 percentage points in some studies. The model wasn't programmed to discriminate. It learned to.

There's also the problem of feedback loops compounding errors. If a content recommendation system learns that provocative content gets more clicks, it serves more provocative content. More clicks follow. The model concludes provocative content is what people want, and pushes it harder. The system isn't malicious — it's optimising for what users appear to reward. The 2021 Facebook whistleblower Frances Haugen presented internal research to the US Senate suggesting that Instagram's recommendation algorithms were amplifying body-image content for teenage girls precisely because it drove higher engagement metrics.

The core issue is that engagement is not the same as wellbeing. AI systems trained on what people click don't automatically learn what's good for people — they learn what's sticky. Separating those two things is an active research challenge, and there's no clean solution yet.

What can you actually do about it?

You're not powerless here — though the levers are limited and imperfect.

Most major platforms offer some degree of data control. Under Europe's GDPR, users have the right to request what personal data a company holds and to have it deleted. California's CCPA gives similar rights to US residents. In practice, deleting your data from a company's servers doesn't necessarily remove its influence from an already-trained model — the patterns your behaviour contributed may be embedded in weights that can't be surgically reversed. This is called the right to be forgotten problem, and it's an open legal and technical debate.

There are more direct behavioural options:

Use explicit feedback controls. When platforms like YouTube or Spotify offer 'don't recommend this', use them. These signals are weighted heavily in personalisation algorithms.- Clear your watch or search history periodically. Most platforms treat recent behaviour as more predictive than old behaviour — resetting history recalibrates recommendations.- Use incognito or private browsing for exploratory searches you don't want to influence your profile.- Opt out of data sharing for model training where offered — Apple, for example, allows users to opt out of contributing data to improve Siri.

The deeper point is that your data is a form of labour. You generate it, companies use it to build products, and you generally receive no compensation beyond the service itself. A growing academic movement — led in part by economists studying 'data as capital' — argues this dynamic needs rethinking. Whether that leads to regulation, compensation models, or user-owned data cooperatives is still being figured out. But awareness is the first step. Every click teaches something. Knowing that changes how you click.

AI learning from your data isn't a side effect — it's the product. These systems are only as intelligent as the human behaviour they're trained on, which means they reflect our patterns, our biases, and our worst clicking habits right back at us. Understanding the mechanism doesn't make you cynical — it makes you a more deliberate participant. Every interaction is a small vote for what the system becomes next. Cast yours intentionally.

Originally published on SnackIQ

Why AI Hallucinations Trick Your Brain

SnackIQ — Fri, 22 May 2026 08:01:53 +0000

Why AI hallucinations happen explained simply: language models don't retrieve facts the way a search engine does — they predict the most statistically likely next word, which means they can generate confident, grammatically perfect lies without any internal alarm bell firing. OpenAI's own September 2025 research paper states directly that hallucinations persist because standard training rewards guessing over acknowledging uncertainty. The result is an AI that sounds authoritative precisely when it is most wrong. Studies suggest that users reading fluent, well-structured AI text accept its claims at dramatically higher rates than they would for obviously rough or uncertain-sounding sources. That's not a quirk of AI. It's a quirk of you.

What actually is an AI hallucination?

The word 'hallucination' is deliberately chosen — and slightly misleading. It suggests the AI is experiencing something. It isn't.

An AI hallucination is any instance where a language model generates a statement that is plausible-sounding but factually false. The model isn't confused or dreaming. It has no awareness of truth at all. It is doing exactly what it was trained to do: produce text that follows statistically likely patterns. The problem is that truth and statistical likelihood are not the same thing.

OpenAI researchers demonstrated this starkly. When they asked a widely used chatbot for the title of a PhD dissertation written by Adam Tauman Kalai — one of the paper's own authors — the system confidently produced three different answers across separate queries. None were correct. When asked for his birthday, it gave three different dates. All wrong. The model wasn't malfunctioning. It was performing normally.

This is the core distinction most people miss. A hallucination isn't a bug in the traditional sense. It's an emergent property of how these systems are built. Language models like GPT-4, Claude, or Gemini are trained on vast datasets of human text — hundreds of billions of words — and they learn to predict what word should come next given everything that came before. They become extraordinarily good at sounding human. They never become good at knowing what's real.

IBM's research team categorises hallucinations into a few distinct types: factual errors (invented statistics, wrong dates, fake citations), intrinsic hallucinations (contradicting the source material the model was given), and extrinsic hallucinations (adding plausible-but-unverifiable details that weren't in the source at all). Each type exploits a different vulnerability in human reading habits.

Why does the training process build lying in?

Here's the uncomfortable truth: AI systems hallucinate in part because we trained them to.

The dominant method for training large language models involves a process called Reinforcement Learning from Human Feedback (RLHF). Human raters evaluate model outputs and score them. The model learns to produce responses that score highly. The problem, as OpenAI's 2025 research argues, is that human raters consistently prefer confident, fluent, detailed answers over honest expressions of uncertainty. An answer that says 'I'm not sure, but possibly...' scores lower than one that says 'The answer is X' — even when X is wrong.

The model learns a perverse lesson: guessing confidently is rewarded, admitting ignorance is not. It is, in a sense, trained to bluff.

This compounds with the fundamental architecture. A language model doesn't store facts in retrievable slots the way a database does. It encodes statistical patterns across billions of parameters. When you ask it a question, it doesn't 'look up' an answer — it generates one from those encoded patterns. For common, well-documented topics, the patterns are dense and reliable. For obscure topics — a specific researcher's dissertation, an unusual medical case, a niche historical event — the patterns are sparse, and the model fills the gap with whatever fits statistically.

Researchers at Stanford and other institutions studying AI reliability have found that hallucination rates vary enormously by domain. Medical and legal queries — precisely the areas where accuracy matters most — tend to produce higher error rates because the training data is thinner and less consistent.

Common knowledge questions: relatively low hallucination rates
Specific citations, names, dates: high hallucination risk
Medical diagnoses and legal precedents: high risk, high stakes
Recently occurred events: very high risk due to training data cutoffs

Newer reasoning models like GPT-5 have significantly reduced hallucination rates — particularly for structured tasks — but OpenAI itself acknowledges they still occur. No current model has solved the fundamental problem.

Why does your brain fail to catch AI mistakes?

The AI's training problem is only half the story. The other half is yours.

Your brain did not evolve to fact-check fluent prose. It evolved to extract meaning from language quickly, rewarding comprehension rather than verification. When you read something that is grammatically correct, logically structured, and written with apparent authority, your brain's cognitive fluency mechanism kicks in — a well-documented psychological effect where easy-to-process information is automatically judged as more credible.

Psychologists have studied cognitive fluency for decades. The core finding, associated with researchers like Rolf Reber and Norbert Schwarz, is that the ease with which your brain processes information directly inflates your confidence in its accuracy. AI-generated text is, almost by design, extremely fluent. It is trained on the best human writing. It rarely stumbles syntactically. It uses hedging language strategically. It sounds like an expert.

This interacts with a second cognitive bias: authority bias. When we perceive a source as knowledgeable — and a confident, detailed AI response pattern-matches our idea of expertise — we lower our critical guard. Studies in cognitive psychology consistently show that people apply less scrutiny to statements from perceived authorities. The AI has no credentials, but it performs credential-like behaviour fluently.

There's a third trap. AI responses often contain a mixture of accurate and inaccurate information. The accurate parts, which you can intuitively verify, act as an anchoring signal that the whole response is trustworthy. Your brain confirms what it recognises, and extends that trust to the parts it can't confirm. Researchers call this the 'Moses illusion' effect in a different context — you accept the whole package when parts of it feel right.

The net result: hallucinated content from AI is specifically well-adapted to bypass your critical thinking, not because anyone designed it that way, but because fluency and confidence are exactly the features that training optimises for.

Can you actually spot an AI hallucination in the wild?

Most people believe they can spot AI errors. Research suggests they dramatically overestimate this ability.

Studies examining people's ability to distinguish AI-generated from human-written text generally find accuracy rates only slightly above chance — and this is for detecting AI writing at all, before you even get to detecting specific factual errors within it. Specific false claims embedded in otherwise accurate text are even harder to catch, because the surrounding accuracy provides constant reassurance.

There are, however, reliable hallucination red flags worth knowing:

Hyperspecific details on obscure topics — exact dates, full names, precise statistics on niche subjects. These are where language models guess most aggressively.
Citations that look real but aren't — a paper title, journal name, and author combination that sounds plausible. Always verify these independently.
Consistent confidence regardless of topic — real experts hedge more on complex questions. Uniform certainty across wildly different topics is a structural feature of AI, not a sign of expertise.
Details that can't easily be checked — claims about private individuals, internal company decisions, unpublished research.

OpenAI's research specifically flags that even GPT-5 — their most capable model as of 2025 — still hallucinations on what they call 'knowledge boundary' questions: situations where the model simply doesn't have reliable training data. The model cannot reliably identify its own knowledge boundaries, so it doesn't warn you when it's in territory where guessing replaces knowing.

The practical implication is uncomfortable: the more you rely on AI for high-stakes information, the more you need to verify it elsewhere. AI tools are extraordinarily useful for drafting, summarising, and exploring ideas. They are genuinely risky as sole sources for anything factual that you haven't independently confirmed.

Will AI ever stop hallucinating?

This is the question researchers disagree on most sharply — and the honest answer is that nobody knows.

The optimistic case: hallucination rates are falling with each model generation. OpenAI's research notes that GPT-5 shows substantially fewer hallucinations than its predecessors, particularly in reasoning-heavy tasks where step-by-step logic acts as a natural check. Retrieval-augmented generation (RAG) — a technique where models fetch verified information from external databases before responding — has shown real promise for reducing factual errors in specific domains. Models can also be trained to express calibrated uncertainty, saying 'I don't know' more reliably.

The pessimistic case: the architecture itself may have a ceiling. Because language models work through pattern completion rather than knowledge retrieval, there may be a fundamental limit to how certain they can be about low-frequency facts. A model trained on a trillion words will still have encountered rare facts far less often than common ones, and sparse training signal equals unreliable output. Some researchers argue that solving hallucination entirely would require fundamentally different architectures — not just better training of current ones.

For now, the realistic picture is improvement without elimination. IBM's AI safety researchers frame this well: hallucination is not a problem to be solved completely, but a risk to be managed and disclosed. That means robust verification tools, clearer AI uncertainty signals in interfaces, and — crucially — user education about where and why these systems fail.

The most important shift may be cultural rather than technical. Treating AI outputs as drafts requiring verification, rather than answers requiring acceptance, changes how the brain engages with the content from the start. That single reframe does more to protect you from hallucinations than any technical fix currently available.

AI hallucinations aren't a temporary glitch waiting to be patched. They're a structural consequence of how language models are built — and they're perfectly calibrated to exploit the same cognitive shortcuts your brain uses to process language efficiently. The fluency that makes AI output feel reliable is the exact quality that makes its errors so hard to catch. Knowing this doesn't mean distrusting AI entirely. It means adjusting the question from 'is this answer correct?' to 'where would I check if it isn't?' That shift in posture is the most powerful tool you have.

Originally published on SnackIQ

7 Ways AI Secretly Ruins Your Privacy

SnackIQ — Tue, 19 May 2026 14:02:21 +0000

How AI affects your privacy is a bigger problem than most people realise — and the mechanism is almost invisible. A 2023 white paper from Stanford University's Human-Centered AI Institute (Stanford HAI) found that AI systems pose risks that go far beyond the data collection scandals of the early internet era. AI doesn't just collect your data. It synthesises it, infers things you never disclosed, and connects dots across sources you'd never link together yourself. Jennifer King, a privacy and data policy fellow at Stanford HAI, described it bluntly: the danger isn't what you share. It's what AI can deduce from it. Every app you open, every sentence you type, every face in every photo you upload — all of it feeds systems that are getting smarter at knowing you than you know yourself.

Your Keystrokes Tell AI More Than Your Words Do

Most people think privacy means keeping secrets. AI doesn't need secrets. It just needs your behaviour.

As technology writer Troy Lowry, a CIO with decades of enterprise experience, pointed out: software like Microsoft Word doesn't just save your final document. It stores every individual keystroke — every delete, every pause, every rewrite. That data exists so you can restore earlier versions. But it also creates a behavioural fingerprint. How long you hesitated before typing a word. Which sentences you wrote and then deleted. What you almost said.

Now scale that up. Every app on your phone logs interaction patterns. Your email client records open times, reply delays, and which threads you ignore. Your browser stores not just where you went, but how long you spent on each page and where your cursor hovered. Individually, none of this feels sensitive. Aggregated by AI, it builds a remarkably accurate psychological profile.

Research in behavioural analytics suggests that typing patterns alone can reveal emotional state, cognitive load, and even early indicators of neurological conditions. AI systems trained on these signals don't need you to confess anything — they watch how you behave and infer the rest. The unsettling part is that this data often exists in corporate systems for years, largely unsynthesised — until an AI model is pointed at it.

AI Training Data Was Probably Scraped From Your Life

When a large language model or image-generation system gets released, the public conversation focuses on what it can do. Almost nobody asks where it learned to do it.

AI models are trained on enormous datasets scraped from the public internet — books, websites, social media posts, images, forum threads. If you've posted publicly online at any point in the last 20 years, there is a reasonable chance your words, your face, or your creative work contributed to training a commercial AI product without your knowledge or consent.

Stanford HAI's Jennifer King flagged this as one of the most underappreciated risks of the current AI boom. Unlike traditional data collection — where a company holds your data and you have some theoretical right of access — training data is absorbed into a model's weights. You can't retrieve it. You can't delete it. It doesn't sit in a database with your name attached; it becomes part of how the system thinks.

This creates a specific legal and ethical problem. The EU's GDPR includes a right to erasure — the so-called "right to be forgotten." But when your data has been baked into a neural network's billions of parameters, there is currently no reliable technical method to remove it. The data is gone, and you are still in it.

Image generators trained on artists' portfolios scraped without permission sparked major lawsuits in 2023. But the same dynamic applies to anyone who ever wrote a public review, posted a photo, or commented on a news article.

Facial Recognition Turns Public Space Into a Database

Walking down a street used to be anonymous. AI changed that.

Facial recognition technology can now identify individuals in real time from CCTV footage, social media photos, or even images captured at public events. The underlying models are often trained on billions of photos scraped from platforms like Facebook, Flickr, and Instagram — photos that users posted with no expectation they'd fuel surveillance infrastructure.

Clearview AI, a US-based company, built a database of over 30 billion facial images scraped from the internet and sold access to law enforcement agencies across multiple countries. In 2022, Clearview was fined £7.5 million by the UK's Information Commissioner's Office and ordered to delete all UK residents' data. Italy, France, Greece, and Australia issued similar rulings. The technology didn't stop.

The privacy problem isn't just government surveillance. Private venues, retailers, and employers have deployed facial recognition systems that log who enters, when, and how often — often without any posted notice. Research by the American Civil Liberties Union (ACLU) found that commercial facial recognition systems showed significantly higher error rates for darker-skinned faces and women, meaning the technology doesn't just surveil — it surveils unevenly.

Your face is biometric data. Unlike a password, you can't change it.

AI Infers Things You Deliberately Never Shared

This is the part that surprises people most. You don't have to disclose something for AI to know it.

Inference is AI's most quietly powerful privacy threat. Given enough behavioural data — your location patterns, purchase history, search queries, and app usage times — AI systems can deduce things you actively chose not to share. Sexual orientation. Political beliefs. Mental health status. Pregnancy. Financial stress.

A widely discussed study by researchers at Cambridge University demonstrated that Facebook likes alone could predict personality traits, political affiliation, and sexual orientation with accuracy that beat self-reported data from friends and family. That was before large-scale AI models existed. Modern inference engines are substantially more powerful.

IBM's research on AI privacy identifies this as the "secondary use" problem: data collected for one purpose gets repurposed by AI systems to generate insights the user never consented to provide. Your fitness tracker data, collected to count your steps, might be used to infer stress levels. Your grocery loyalty card, collected to give you discounts, might be used to infer whether you're pregnant.

The disturbing commercial case came in 2012 when Target's analytics system reportedly identified a teenage customer as pregnant based on shopping patterns — before she had told her family. AI has become exponentially better at this kind of inference since then. The gap between what you share and what AI knows is closing fast.

Your AI Chatbot Conversations Aren't As Private As You Think

People tell chatbots things they wouldn't say to a search engine. That's a problem.

When you type a sensitive question into a chatbot — about a medical symptom, a legal situation, a relationship problem — it feels like a private conversation. It isn't. Stanford HAI's white paper specifically flagged that prompts submitted to AI chatbots may be retained, reviewed by human employees for safety and quality purposes, or in some jurisdictions, shared with law enforcement on request.

In 2023, Samsung engineers made headlines when they inadvertently leaked proprietary source code and internal meeting notes by pasting them into ChatGPT — not understanding that their inputs were being used to improve the model. Samsung subsequently banned generative AI tools on company devices. The same dynamic applies to individuals: health details, financial information, and personal disclosures shared with chatbots may persist in training pipelines.

Most major AI platforms have updated their privacy policies to allow opting out of training data use — but the default settings often still capture your conversations. The burden falls on you to find the setting, understand it, and change it.

There's also the aggregation issue. A single chat session reveals little. But months of conversations with an AI assistant — asking about your symptoms, your finances, your relationships — creates a longitudinal record of your inner life that no previous technology has ever had access to.

Workplace AI Surveillance Is Already Monitoring You

Your employer almost certainly knows more about your workday than you think. AI just made it cheaper and easier to act on that knowledge.

As Lowry described from his experience as a university CIO: the data to track every website visited, every minute of screen time, every keystroke in every document has existed in corporate systems for years. The barrier wasn't capability — it was the human cost of synthesising it. AI removes that barrier.

Workplace monitoring tools powered by AI now track mouse movement frequency, keystrokes per minute, application focus time, video call engagement via facial expression analysis, and email sentiment. Companies like Microsoft, through its Productivity Score feature (later renamed after public backlash), built dashboards that gave managers visibility into individual employees' communication patterns across Teams, Outlook, and SharePoint.

A 2023 survey by the American Management Association found that the majority of large US companies monitor employee digital activity in some form. AI-powered tools have made this monitoring cheaper, more granular, and harder for employees to detect.

Email sentiment analysis flags employees showing signs of disengagement- Screen-time trackers log which applications are active and for how long- Meeting analytics measure how often you speak, interrupt, or go silent- Badge data combined with digital logs can reconstruct your physical movement through an office

In most jurisdictions, this is entirely legal — provided employees are notified in their contracts, which they usually are, buried in a document nobody reads.

Data Brokers Are Feeding AI Systems You've Never Heard Of

You've never signed up for a data broker's service. You're almost certainly in their database anyway.

Data brokers are companies that collect personal information from hundreds of sources — public records, loyalty programmes, website trackers, social media, app permissions — and sell it to marketers, insurers, employers, and increasingly, AI developers. The Federal Trade Commission (FTC) in the US has identified over 4,000 data broker companies operating in the American market alone. Most consumers have no idea this industry exists.

The connection to AI privacy is direct. AI systems need training data, and data brokers have massive, richly labelled datasets about real people's behaviour, preferences, locations, and purchasing patterns. When an AI model learns to predict consumer behaviour or identify creditworthiness, it may be learning from profiles assembled without a single direct interaction with the person being profiled.

Stanford HAI's Jennifer King noted that the core risk here is that AI amplifies the existing surveillance economy by making previously unwieldy data immediately actionable. A data broker's file on you might contain hundreds of data points that, read by a human analyst, would require hours to process. An AI can synthesise it in milliseconds and generate a prediction — about your health, your finances, your politics — that follows you invisibly into credit decisions, insurance pricing, and targeted advertising.

The chain from data collection to AI inference to real-world consequence is now faster than any regulatory framework can track. California's Consumer Privacy Act (CCPA) gives residents the right to opt out of data broker sales — but exercising that right requires contacting hundreds of companies individually.

Privacy used to be about what you chose to reveal. AI has fundamentally changed that equation. The threat now isn't that someone reads your diary — it's that a system you've never interacted with builds a more accurate version of you than your diary ever contained, using data you didn't know you were generating. The seven mechanisms above aren't bugs in AI development. They're features of how these systems work. Understanding them doesn't require paranoia. It requires the same sceptical curiosity you'd apply to anything that knows too much about you.

Originally published on SnackIQ

How AirTags Actually Track You

SnackIQ — Mon, 18 May 2026 08:02:08 +0000

AirTags track location through one of the most quietly powerful networks ever built — a mesh of over one billion iPhones that most of their owners don't even know they're part of. When an AirTag is separated from its owner, it doesn't use GPS. It doesn't need a SIM card or a data plan. Instead, it emits a constant Bluetooth signal, and any nearby iPhone that picks it up anonymously reports its location back to Apple. That data reaches the owner in seconds. Apple launched AirTags in April 2021, pricing them at $29 each. By design, the process is invisible, encrypted, and — according to Apple — impossible for anyone, including Apple itself, to read. Whether you've used one or simply found one in your bag, understanding exactly how this technology works changes how you see every iPhone you walk past.

What actually happens when an AirTag goes missing?

The moment an AirTag leaves Bluetooth range of its owner's iPhone — roughly 10 metres in open air — it enters what Apple calls Lost Mode. This is where the real magic happens.

The tag starts broadcasting a rotating Bluetooth identifier roughly once per second. It can't send this signal to Apple directly. It has no GPS chip, no Wi-Fi radio, no cellular antenna. By weight, an AirTag is 11 grams. By capability, it's intentionally stripped down.

What happens next depends entirely on foot traffic. When another iPhone passes within Bluetooth range, that phone's Find My software — running silently in the background — detects the AirTag's signal. The passing iPhone then packages the tag's encrypted location data and uploads it to Apple's servers. The owner gets a notification showing exactly where their item is.

The person carrying that passing iPhone has no idea any of this happened. Their phone doesn't display a notification. No battery is meaningfully drained. No permission prompt appears. Apple designed the entire process to be invisible to the relay device. This is why AirTags work in a way GPS trackers alone never could — GPS tells you where you are, but it doesn't help you if nobody's watching. The Find My network is always watching, everywhere.

The network's density is what makes it extraordinary. Apple has never published exact figures, but analysts estimate over one billion active Apple devices participate globally. In any major city, the odds of an AirTag going more than a few minutes without a relay ping are vanishingly small.

Why does Ultra-Wideband make AirTags different from all other trackers?

Bluetooth tells you an AirTag is nearby. Ultra-Wideband (UWB) tells you exactly which direction to walk and how far to go. That distinction matters enormously.

UWB is a short-range radio technology that measures the precise time it takes a signal to travel between two devices. Because radio waves move at a known speed, tiny differences in arrival time translate into centimetre-level distance measurements. Standard Bluetooth can tell you something is within 10 metres. UWB can tell you it's 2.3 metres to your left and slightly below you.

Apple's Precision Finding feature, available on iPhone 11 and later models with a UWB chip (branded as the U1 or U2 chip), uses this to give visual and haptic guidance. Your phone displays an arrow. The arrow updates in real time as you move. A distance readout counts down. When you're within arm's reach, your phone buzzes with a short pulse. Finding a lost AirTag in a dark car park or under a pile of coats goes from a game of hot-and-cold to a ten-second retrieval.

Not every device supports this. Older iPhones and all Android devices fall back to standard Bluetooth proximity detection, which is less precise but still functional. This creates a two-tier experience — Apple device owners get centimetre-accurate navigation, everyone else gets a general area.

UWB range: approximately 10–20 metres- UWB accuracy: centimetre-level directional precision- Bluetooth fallback range: up to 30 metres in open space- Devices with UWB support: iPhone 11 and later (not SE series)

The CR2032 coin battery that powers all of this lasts approximately one year under normal use — a remarkable feat given how frequently the tag is broadcasting.

How does Apple keep the location data private?

AirTags traffic in one of the most sensitive data types imaginable: the physical location of real objects belonging to real people. Apple's privacy architecture was therefore, at launch, its most scrutinised design choice.

Every AirTag uses end-to-end encryption combined with rotating Bluetooth identifiers. The tag's identifier changes on a regular schedule, derived from a cryptographic key stored only on the owner's Apple account. A relay iPhone picks up a Bluetooth signal and uploads it — but it cannot decode what it's carrying. Apple's servers store the location report, but Apple states it cannot decrypt the data either. Only the owner's device, holding the matching private key, can unlock the location.

This architecture means the system is built like a sealed envelope passing through many hands. The relay devices are postmen who never read the letter. The post office stores it but can't open it. Only the addressee can.

Apple also publishes the cryptographic specification for the Find My network, allowing independent security researchers to audit the claims. Researchers at institutions including the Technical University of Darmstadt in Germany have analysed the protocol and confirmed the core privacy properties hold — though they have noted theoretical edge cases involving large-scale traffic analysis.

In practice, this means your iPhone is constantly relaying location data for AirTags and other Find My accessories it passes, and no individual record can be traced back to your device. The privacy cost to relay devices is genuine — your phone does this automatically — but the exposure is designed to be negligible.

Can AirTags be used to stalk someone?

Yes — and Apple knew this before launch. The anti-stalking measures built into AirTags are, in some ways, the most technically interesting part of the product.

When an AirTag that isn't paired to your Apple ID has been travelling with you for a period of time, your iPhone alerts you. The alert says an unknown AirTag is moving with you and offers the option to play its speaker tone to locate it. Android users are not left entirely unprotected either — Apple released an Android app called Tracker Detect, and Google later integrated passive AirTag scanning into Android itself.

The AirTag also plays an audible chime after being separated from its owner for an extended period — originally set at three days, then shortened to somewhere between 8 and 24 hours following criticism from domestic abuse advocates. The chime is designed to reveal itself to whoever is being unknowingly tracked.

Despite these measures, documented cases of AirTags being used for stalking emerged within months of launch. Police departments across the United States and the United Kingdom reported incidents. In response, Apple updated its unwanted tracking alerts to trigger faster and made the chime louder. The company also began working with law enforcement to assist investigations — AirTags have a serial number that Apple can link to the Apple ID used to activate them, with a valid legal request.

The core tension is real: any technology precise enough to find your lost luggage is precise enough to track a person without consent. Apple's countermeasures are genuine, but no passive alert system perfectly catches every case. Being aware of this is the first defence.

What happens if you find an AirTag that isn't yours?

Finding an unknown AirTag — whether it beeped at you, you received a phone alert, or you simply spotted one — is more common than most people expect. Knowing what to do matters.

If your iPhone shows an 'AirTag Found Moving With You' notification, tap it. Apple's interface walks you through playing the tag's sound, viewing its serial number, and disabling it. Disabling an AirTag is simple: twist the back counterclockwise, remove the CR2032 battery, and the tag goes completely silent and invisible to the Find My network. It cannot be re-enabled without its owner physically replacing the battery.

The serial number is also readable via NFC on any smartphone — iPhone or Android. Hold your phone near the white side of the AirTag and the device will open a webpage showing the tag's serial number and whether Apple has marked it as lost (in which case a contact number may be displayed). This is how legitimate lost-property recovery is supposed to work.

If you have reason to believe the AirTag was placed on you without consent, both Apple and law enforcement recommend keeping it for evidence rather than destroying it. The serial number links to an Apple ID, and Apple cooperates with legal requests.

The bottom line: the same system that makes AirTags extraordinarily useful for tracking luggage, keys, and bags through crowded airports also creates real risks. Understanding the mechanism — the billion-device relay network, the UWB precision, the rotating cryptographic identifiers — gives you the knowledge to use them well and recognise when someone else is using one against you.

AirTags are a study in invisible infrastructure. A $29 disc with no GPS chip, no SIM, and a battery the size of a shirt button can locate itself anywhere in a city — because it doesn't do the work alone. Every iPhone you walk past is doing it. That's either a remarkable feat of cooperative engineering or a reminder that the network in your pocket serves more masters than just you. Probably both. Knowing exactly how the system works is the only way to decide which side of that trade-off you're comfortable with.

Originally published on SnackIQ

How AI Actually Reads Your Writing

SnackIQ — Sat, 16 May 2026 14:03:07 +0000

Every time you type a message to an AI, something genuinely strange happens. The system doesn't read your words the way you do. It never learned language from a parent, never felt confusion, never looked up a word in a dictionary. Yet AI language models — including the ones powering ChatGPT, Gemini, and Claude — process human writing with enough sophistication to summarise legal contracts, translate poetry, and debug code. According to Stanford's 2024 AI Index Report, over 60% of knowledge workers now use AI writing tools weekly. So what is actually happening when artificial intelligence reads your words?

Words Don't Mean Anything to AI Until They Become Numbers

Before an AI model processes a single word you write, it strips language of everything that makes it feel like language. No letters. No grammar. No meaning. Just numbers.

The process starts with tokenisation — breaking your text into small chunks called tokens. A token is roughly three to four characters. The word "reading" becomes one token; the phrase "artificial intelligence" becomes three. GPT-4, OpenAI's flagship model, processes text in chunks of up to 128,000 tokens at a time, which is roughly the length of a full novel.

Each token is then converted into a vector — a long list of numbers, often 768 to 12,288 values depending on the model. This numerical fingerprint encodes something surprisingly powerful: the word's relationship to every other word the model has ever encountered. Words with similar meanings cluster near each other in this mathematical space. "King" and "queen" are close. "Happy" and "joyful" are close. "Banana" and "justice" are not.

This is called an embedding, and it's the foundation of how AI reads. The model doesn't know what "lonely" feels like. But it knows that "lonely" appears in contexts similar to "isolated", "alone", and "melancholy" — and it encodes that relational knowledge numerically. That statistical proximity does a surprising amount of work.

Why Context Changes Everything the AI Thinks You Mean

The word "bank" means a financial institution. It also means the side of a river. And a verb for tilting in aviation. Human readers resolve this instantly from context. For decades, computers couldn't.

The breakthrough came in 2017, when a team at Google published a paper introducing the Transformer architecture — the technology underlying virtually every major AI language model today. The key innovation was something called "attention": a mechanism that lets the model weigh how much each word in a sentence should influence the interpretation of every other word.

When you write "I went to the bank to deposit a cheque", the attention mechanism links "bank" strongly to "deposit" and "cheque", downweighting "river" as a possible meaning. When you write "The kayak drifted toward the muddy bank", the same word gets a different interpretation because "kayak" and "muddy" pull the attention in a different direction.

This happens across the entire passage simultaneously — not word by word, left to right, but in a kind of parallel sweep across all tokens at once. The result is that AI can hold the meaning of a paragraph in mind while reading its last sentence, in a way earlier systems simply couldn't.

Research from institutions including MIT and Stanford has shown that Transformer models develop internal representations that loosely correspond to grammatical structure, even though they were never explicitly taught grammar. The model infers rules from patterns, billions of times over.

What 'Understanding' Actually Means for a Language Model

Here's where it gets philosophically murky — and where most popular coverage gets it wrong.

When an AI reads your writing and produces a coherent, relevant response, it feels like understanding. But the mechanism underneath is statistical prediction. The model is calculating, at each step, which token is most likely to come next given everything that preceded it. It has seen so many examples of human text that its predictions are extraordinarily well-calibrated — but prediction is not comprehension.

Linguist Noam Chomsky and his collaborators have argued that large language models are fundamentally different from human language acquisition. Children learn language from a tiny amount of data relative to what AI requires, and they learn it by grounding words in physical experience — objects, faces, cause and effect. AI learns purely from text, with no sensory grounding at all.

That distinction matters in practice. AI models are known to confidently produce plausible-sounding falsehoods — a failure mode called hallucination — because they're optimised for fluent output rather than factual accuracy. A human who doesn't know something usually knows they don't know it. An AI fills the gap with statistically likely content instead.

None of this means AI language processing is useless. It means it's a different kind of reading. Extraordinarily powerful in some respects, structurally blind in others.

How AI Picks Up on Tone, Style, and Subtext

Ask an AI to make your email "more professional" or your essay "more conversational", and it will do it reliably well. That's not an accident — and it's not magic.

During training, AI models are exposed to enormous varieties of human writing style. Formal legal documents. Casual Reddit threads. Academic papers. Sales copy. Literary fiction. Each of these registers has statistical fingerprints: formal writing uses longer sentences, Latinate vocabulary, and passive constructions; casual writing uses contractions, shorter sentences, and colloquialisms. The model learns these patterns implicitly.

When you ask it to adjust tone, you're essentially asking it to shift toward a different region of the probability distribution it learned during training. It doesn't feel the difference between "formal" and "casual" — but it has seen enough examples of each to reproduce the surface patterns convincingly.

Subtext is trickier. Research using AI-generated text detection has found that models sometimes miss sarcasm, irony, and culturally-specific implication — especially when those cues are subtle or depend on shared lived experience. The model can recognise patterns it has seen before, but genuinely novel emotional nuance often slips through.

Explicit sentiment ("I love this", "I hate this") — AI detects reliably
Implied sentiment ("Oh, great, another Monday") — usually caught via pattern recognition
Deep irony or cultural subtext — frequently missed or misread

This is why AI writing assistants work brilliantly for structure and clarity but can struggle with voice.

Why Your Prompt Wording Changes Everything

If you've ever noticed that rephrasing a question gets a dramatically different answer from an AI, you've encountered something researchers call prompt sensitivity — and it reveals something important about how AI reading actually works.

Because AI interprets meaning statistically rather than logically, small wording changes can shift which patterns activate. Asking "What are the weaknesses of this argument?" produces a different internal pathway than "Play devil's advocate against this argument" — even though the intent is nearly identical. The second phrasing triggers patterns associated with debate and counterargument; the first triggers patterns associated with critical analysis.

Studies from leading AI labs have found that chain-of-thought prompting — asking a model to "think step by step" before answering — measurably improves performance on reasoning tasks. The model hasn't become smarter. You've simply activated a different region of its learned statistical patterns. That's a remarkable property of a system that is, at bottom, just predicting the next token.

Practical upshot: the AI is reading your prompt with extreme sensitivity to phrasing. Specificity, framing, and explicit instructions about format all shape the output significantly. Vague prompts produce vague results not because the AI is being lazy, but because vague prompts match patterns from vague contexts in training data — and the model mirrors that back.

AI reading isn't human reading. It never was. The model converts your words into numbers, measures their statistical relationships, and predicts what should come next — billions of parameters firing in parallel, all calibrated on the vast record of human writing. That's genuinely impressive. It's also genuinely different from comprehension. Once you understand that, AI stops feeling either magical or disappointing. It's a sophisticated pattern-matching system built on the entire written output of our species. Use it accordingly — with clear prompts, healthy scepticism, and an awareness that the "reading" happening on the other end is unlike any reading you've ever done.

Originally published on SnackIQ

How AirDrop Actually Works Its Magic

SnackIQ — Fri, 15 May 2026 08:02:01 +0000

AirDrop transfers files between Apple devices in seconds — no cable, no cloud, no login. It feels like magic, but it's actually a precise two-radio handshake that most people don't know exists. Apple introduced AirDrop in 2011, and it's been quietly running on Bluetooth 4.0 and Wi-Fi Direct ever since. The technology doesn't route your files through Apple's servers. Your photo takes a direct, encrypted path from one device to another — often faster than emailing it to yourself. According to Apple's own platform documentation, transfers happen over a dedicated peer-to-peer Wi-Fi connection that can sustain speeds far beyond what Bluetooth alone could ever manage. Understanding how it actually works changes how you think about wireless technology — and explains why it sometimes fails in ways that seem completely random.

Why does AirDrop need Bluetooth if Wi-Fi does the heavy lifting?

This is the question that unlocks everything. Most people assume AirDrop is just Bluetooth file sharing — it's not. Bluetooth is only used for discovery, not for the actual transfer. The two radios play entirely different roles, and neither one can do the job alone.

When you open AirDrop on your iPhone or Mac, your device starts broadcasting a short Bluetooth Low Energy signal. This signal doesn't carry your file — it just announces your presence to nearby Apple devices within roughly 9 metres. Think of it like raising your hand in a room. It uses almost no battery and contains no personal information in plain text.

When a compatible device picks up that signal and a transfer is initiated, the two devices do something more sophisticated. They negotiate a direct Wi-Fi connection using Apple Wireless Direct Link, a peer-to-peer protocol built on top of Wi-Fi that doesn't require a router. Your home network isn't involved. Neither is any Wi-Fi hotspot. The devices create a private, encrypted channel directly between themselves.

Once that Wi-Fi link is established, the actual file transfer happens across it at speeds that can exceed 100 Mbps in ideal conditions — far faster than Bluetooth's practical ceiling of around 3 Mbps. A 50-megabyte video file that would take nearly three minutes over Bluetooth transfers in a few seconds via the Wi-Fi channel.

This is why both radios need to be switched on for AirDrop to work. Turning off Bluetooth kills discovery. Turning off Wi-Fi kills the transfer channel. Either one missing and nothing happens — which explains one of the most common AirDrop failure modes people encounter.

How does your iPhone stay private while still being discoverable?

Privacy is where AirDrop's engineering gets genuinely clever — and where Apple made decisions that weren't obvious.

When your device broadcasts that Bluetooth discovery signal, it doesn't simply shout your Apple ID or phone number into the air. Instead, it transmits a hashed, partial identifier derived from your contact information. A hash is a one-way mathematical transformation: it takes your phone number and produces a scrambled string of characters that can't be reversed to reveal the original number without already knowing it.

When a nearby device picks up your signal, it checks its own contacts list. If it finds a hash that matches yours, it knows you're a known contact and can offer to receive from you. If there's no match, the device either ignores you entirely or shows you as a generic unnamed sender, depending on your AirDrop settings. This process happens silently and automatically in milliseconds.

Researchers at the Technische Universität Darmstadt published a paper in 2021 identifying a potential weakness in this system: because the hash is partial and based on known data like phone numbers, it was theoretically possible to reverse it using brute-force methods in public settings. Apple addressed the vulnerability by updating the protocol in iOS 16 to use a more robust cryptographic approach called PrivateDrop, which uses private set intersection techniques to verify mutual contacts without revealing raw hash values to unknown parties.

Your three AirDrop settings — Off, Contacts Only, and Everyone — map directly to these layers of disclosure. "Everyone" means your device responds to any incoming signal, regardless of hash matching. "Contacts Only" means mutual hash verification is required. "Off" means Bluetooth stops broadcasting entirely.

What actually happens during the split second before a file moves?

There's a hidden negotiation phase that most users never think about — but it's what makes AirDrop feel seamless rather than clunky.

Once discovery is confirmed via Bluetooth and both devices agree to proceed, they exchange TLS certificates — Transport Layer Security, the same encryption standard that protects your banking app. These certificates authenticate each device and establish the encrypted channel over which the file will travel. No certificate exchange, no transfer.

This handshake is why AirDrop transfers are end-to-end encrypted by default. Apple doesn't hold a key. No intermediary server touches the data. The file exists on your device, travels through an encrypted tunnel, and arrives on the recipient's device. It never touches iCloud unless you deliberately save it there afterward.

After the TLS handshake, the sending device packages the file and begins streaming it across the Wi-Fi Direct channel. The recipient sees a preview — the thumbnail you see in that notification — which is generated and transmitted during this pre-transfer window, not after. That preview is a low-resolution version sent ahead of the full file, which is why you can decide to accept or decline before the whole thing has transferred.

The transfer itself uses standard Wi-Fi protocols at the physical layer, which means environmental factors matter. Walls, competing 2.4GHz devices, and distance all affect speed. That's not a flaw in AirDrop specifically — it's physics. Research into Wi-Fi Direct performance consistently shows that throughput degrades with distance and physical obstructions, just as it does with any Wi-Fi signal.

Why does AirDrop sometimes fail for no obvious reason?

AirDrop's failure modes make perfect sense once you understand the two-radio architecture — they just look mysterious from the outside.

The most common reason AirDrop fails is Bluetooth interference. Crowded environments — conference halls, concerts, busy airports — fill the air with competing Bluetooth signals. Your device is trying to broadcast a discovery ping and have it received cleanly in an environment where dozens or hundreds of other devices are doing the same thing. The discovery phase breaks down before the Wi-Fi link ever gets established.

A second failure mode involves the Wi-Fi stack specifically. Some corporate networks and managed Wi-Fi environments block the ad-hoc, peer-to-peer Wi-Fi frequencies that Apple Wireless Direct Link uses. Your device might have Wi-Fi turned on, but the protocol-level requirements for AirDrop's direct connection aren't met. The fix — turning off Wi-Fi and back on, or switching to a different network — works because it resets the Wi-Fi subsystem and renegotiates the available channels.

Software mismatches are a third cause. AirDrop between a Mac running a significantly older version of macOS and an iPhone on the latest iOS can fail because Apple has updated the underlying protocol between versions. The discovery signal goes out, the handshake begins, and then the certificate or encryption negotiation fails quietly.

Bluetooth off — discovery can't happen, device is invisible
Wi-Fi off — transfer channel can't form, even if discovery works
Network interference — ad-hoc Wi-Fi blocked by router settings
Firewall or MDM policies — common on work devices and managed networks
OS version mismatch — protocol changes between major iOS/macOS versions

Understanding these layers means you can diagnose failures systematically rather than cycling through random restarts.

Is AirDrop actually as private as Apple claims?

Apple markets AirDrop as private-by-default, and the core architecture supports that claim. But the complete picture has a few important nuances.

The 2021 Darmstadt research was significant because it demonstrated that in public spaces, the Bluetooth discovery phase could theoretically leak partial identifiers to anyone running specialised scanning hardware. A bad actor in a coffee shop couldn't intercept your files — the transfer itself remained encrypted — but they could potentially match your presence to your phone number if they already had a database of numbers to check against. Apple's PrivateDrop update substantially mitigated this, but the research was a useful reminder that "encrypted" and "undetectable" are not the same thing.

A separate concern involves the "Everyone" setting. When AirDrop is set to receive from everyone, your device responds to discovery signals from any Apple device nearby. A technique sometimes called "AirDrop bombing" — sending unsolicited images to strangers in public — exploited this setting in crowded spaces. In iOS 16.2, Apple limited "Everyone" to a 10-minute window after activation rather than allowing it to remain permanently on, effectively reducing the exposure window.

For everyday use between people you know, AirDrop's privacy model is genuinely robust. The combination of hashed contact verification, TLS encryption, and direct peer-to-peer transfer — with no server in the middle — gives it a stronger privacy profile than most alternatives. Sending a file via email or a messaging app involves at least one third-party server receiving, storing, and forwarding your data. AirDrop, when it works, avoids that entire chain.

What this means practically: keep your setting on "Contacts Only" by default, flip to "Everyone" only when you need it, and flip it back. The security model works best when you're treating the setting as a momentary door rather than a permanently open window.

AirDrop is one of those technologies that looks simple precisely because it's complicated. Two radios, a cryptographic handshake, a private Wi-Fi channel, and a TLS-encrypted tunnel — all assembled in under a second. The failures aren't random; they're physics and protocol behaving predictably. The privacy model isn't perfect, but it's more rigorous than most people give it credit for. Next time a transfer fails in a crowded room, you'll know exactly which radio to blame.

Originally published on SnackIQ

How Much Water Does AI Really Use?

SnackIQ — Wed, 13 May 2026 14:02:14 +0000

How much water does AI use? More than almost anyone realises. A single large-scale AI model training run can consume millions of litres of water. According to research from the University of California, Riverside, generating roughly 20 to 50 short responses from ChatGPT-3 requires about 500ml of water — equivalent to a standard water bottle. Multiply that by hundreds of millions of daily queries and you get a number that rivals entire cities. The Environmental and Energy Study Institute reports that a large data centre can consume up to 5 million gallons of water per day — equivalent to the daily water use of a town of 10,000 to 50,000 people. This isn't a distant industrial problem. Every AI query you run has a water cost, and as the AI boom accelerates, that cost is climbing fast.

How Does AI Actually Use Water?

Most people picture AI as a purely digital thing — electrons, not ecosystems. The water connection feels abstract until you understand what's happening inside the data centres that run these models.

AI workloads generate enormous heat. The processors — particularly the high-end GPUs used for AI inference and training — run at extreme computational intensity for sustained periods. Left unchecked, they'd overheat within minutes. Cooling those chips is what drives water demand.

Data centres cool themselves in two main ways. The first is air cooling, where chilled air is circulated through the facility. The second, and more water-intensive method, is evaporative cooling, where water is evaporated to shed heat into the atmosphere. Think of it as industrial-scale sweating. The water that evaporates doesn't return to the local water supply — it's gone.

AI workloads are significantly more water-intensive than standard computing tasks because they demand sustained, high-density power loads. A Google search might take milliseconds of light processing. Running a prompt through a large language model involves billions of matrix calculations across thousands of chips, all generating heat simultaneously.

There's also a second water cost that gets less attention: the water used to generate the electricity that powers data centres. Thermoelectric power plants — which include coal, natural gas, and nuclear — withdraw large volumes of water for cooling. Depending on the energy mix in a given region, this "upstream" water cost can rival or exceed the direct cooling water used on-site.

Direct water use: evaporative cooling towers at the data centre itself
Indirect water use: water withdrawn by power plants to generate the electricity consumed
Embodied water: water used to manufacture the chips and hardware inside the facility

Most reported figures only capture direct use. The true water footprint of AI is larger than the headline numbers suggest.

AI Water Use vs Everyday Activities

Numbers without context are just noise. The figures become meaningful when you stack AI's water consumption against things you already have an intuition for.

Researchers at the University of California, Riverside — led by computer scientist Shaolei Ren — estimated that training GPT-3 consumed approximately 700,000 litres of fresh water. That's roughly the volume needed to produce 370 BMW cars, or enough drinking water to sustain a person for nearly 2,000 years. A single short conversation with ChatGPT — say, 20 to 50 exchanges — uses around 500ml of water at the data centre level.

The table below compares the direct water footprint of AI tasks against familiar everyday activities, using figures drawn from published research and industry estimates.

Activity	Estimated Water Use	Context
20–50 ChatGPT responses	~500 ml	Equivalent to one standard water bottle
Training GPT-3 (one-time)	~700,000 litres	Enough to fill roughly 280 standard bathtubs
Producing 1 kg of beef	~15,400 litres	One of the most water-intensive food products
Growing 1 kg of almonds	~12,000 litres	Often cited in water footprint debates
One 5-minute shower	~38–75 litres	Varies by flow rate
Washing a full load of laundry	~50–150 litres	Depends on machine efficiency rating
One Google search	~0.3 ml	Far lower intensity than AI inference

The comparison with a Google search is particularly striking. AI inference can use roughly 1,500 times more water per query than a standard web search. That gap reflects the computational difference between retrieving indexed results and generating novel language outputs from scratch.

It's also worth noting that these figures represent direct data centre water use only. Add in the upstream power-generation water and the numbers grow considerably — some researchers estimate the total footprint could be two to three times higher depending on regional energy sources.

Which AI Companies Use the Most Water?

Tech giants have started disclosing their water consumption in annual sustainability reports — though the methodology and completeness of these disclosures varies significantly, making direct comparisons tricky.

Microsoft reported consuming approximately 6.4 billion litres of water in 2022, a figure that rose by around 34% compared to 2021. The company attributed a significant portion of that increase to AI development, including its partnership with OpenAI. Google reported similar trends, with water consumption rising year-over-year as its AI infrastructure scaled up.

Company	Reported Water Use (approx.)	Year	Key Driver
Microsoft	~6.4 billion litres	2022	AI training (OpenAI partnership), data centre expansion
Google	~20.9 billion litres	2022	Cooling across global data centres, AI workloads
Meta	~2.5 billion litres	2022	Data centre operations, AI recommendation systems
Amazon (AWS)	Not fully disclosed	2022	Partial disclosure; water figures embedded in broader sustainability metrics

These numbers need context. Google's 20.9 billion litres sounds astronomical — and it is — but the company operates one of the largest distributed computing networks on Earth, spanning dozens of countries. The concern isn't just volume but location. Data centres built in water-stressed regions, such as the American Southwest or parts of the Middle East, draw from the same aquifers serving local agriculture and residential water supplies.

The Lincoln Institute of Land Policy has flagged this spatial mismatch as a growing policy problem. A data centre in rainy Oregon draws from abundant supplies. The same facility in Arizona competes directly with farmers and municipalities during drought conditions. Some communities have pushed back — in 2022, a proposed Meta data centre in the Netherlands faced resistance after it emerged the facility would consume millions of litres of drinking-quality water daily.

How Does AI Water Use Compare to Other Industries?

Context is everything when evaluating environmental impact. Critics of AI sometimes present its water use as uniquely profligate. Defenders counter that other industries dwarf it. Both are partially right.

Industry / Activity	Annual Global Water Use (estimate)	Notes
Global agriculture	~2,700 billion m³ (2.7 trillion litres)	Accounts for roughly 70% of all freshwater withdrawals globally (UN FAO)
Global thermoelectric power generation	~580 billion m³	Includes water for cooling coal, gas, and nuclear plants
Global industrial manufacturing	~400 billion m³	Includes steel, textiles, chemicals
Global data centres (all computing)	~200–600 billion litres	Estimates vary widely; AI share growing rapidly
US data centres alone	~100–200 billion litres	US hosts the largest concentration of AI infrastructure globally

In absolute terms, agriculture uses several thousand times more water than AI data centres. The fashion industry alone is estimated to use around 93 billion cubic metres of water annually. So the argument that AI is the primary water villain doesn't hold up at a global scale.

But that framing misses the point. The issue isn't total volume — it's trajectory and location. Agriculture has used water intensively for millennia and is increasingly subject to efficiency regulation. AI water use is new, growing at roughly 20–30% per year, and concentrated in specific geographies that often face existing water stress.

Researchers also point out that AI's water footprint is largely invisible to consumers. When you buy beef, the water embedded in its production at least enters your awareness. When you ask a chatbot a question, the water cost is completely hidden. That invisibility makes it harder to pressure companies to improve efficiency or relocate facilities.

Can AI Actually Become Less Thirsty?

The water problem is serious. It isn't necessarily permanent. Several technological and policy approaches are already reducing the water intensity of AI computing — some more mature than others.

Direct-to-chip liquid cooling is one of the most promising hardware solutions. Instead of cooling the entire server room with chilled air or evaporative towers, coolant is routed directly to the chips generating the most heat. This dramatically reduces the volume of water needed because you're cooling the source rather than the surrounding air. Microsoft, Google, and several hyperscale operators have begun rolling out these systems in newer facilities.

Immersion cooling takes this further — submerging servers directly in dielectric fluid that absorbs heat without evaporation. Early deployments show water savings of 90% or more compared to conventional evaporative systems. The technology is mature enough to work but expensive to retrofit into existing facilities.

Cooling Technology	Water Efficiency vs Standard Evaporative	Deployment Status
Evaporative (cooling towers)	Baseline	Dominant method globally
Air-cooled (no water)	~80–100% reduction in direct water use	Used in cooler climates; less effective in heat
Direct-to-chip liquid cooling	~40–60% reduction	Growing adoption in new builds
Immersion cooling	~90%+ reduction	Niche but expanding; higher upfront cost
Recycled/non-potable water sourcing	Reduces freshwater stress (not total volume)	Policy-driven; uneven adoption

Location also matters enormously. Data centres built in cooler climates — Scandinavia, Iceland, the Scottish Highlands — can rely on ambient air cooling for much of the year, dramatically cutting water demand. Several large AI operators have announced northern European facilities partly for this reason.

On the software side, model efficiency improvements reduce the number of computations — and therefore the heat generated — per query. Models like GPT-4 are significantly more computationally efficient per output than their predecessors, even if the total system demand has grown because usage has expanded so rapidly.

Regulation is the wild card. Currently, no country mandates water efficiency standards for data centres the way energy efficiency standards exist for buildings or vehicles. Researchers and environmental advocates are increasingly calling for mandatory Water Usage Effectiveness (WUE) disclosures — a metric that measures litres of water consumed per kilowatt-hour of energy used. Greater transparency would at minimum let communities assess the true cost of hosting a data centre before they sign the tax incentive deal.

AI's water problem isn't a reason to stop using the technology. It is a reason to stop pretending it's weightless. Every prompt has a physical cost — water evaporated, aquifers drawn down, communities competing for the same supply. The good news is that better cooling technology, smarter siting, and meaningful efficiency metrics already exist. What's lagged behind is the political and corporate will to mandate them. The next time you use an AI tool, you're not just sending data into the cloud. You're reaching, invisibly, into a water table somewhere.

Originally published on SnackIQ

Why AI Chatbots Actually Hallucinate

SnackIQ — Mon, 11 May 2026 14:02:14 +0000

Why do AI chatbots hallucinate? Because they were never actually built to tell the truth. They were built to predict the next most plausible word. That distinction sounds subtle. It isn't. OpenAI's own September 2025 research paper acknowledged that even GPT-5 — their most advanced model at the time of publication — still hallucinates, and that the problem persists across all large language models because 'standard training and evaluation procedures reward guessing over acknowledging uncertainty.' In other words, the architecture that makes AI chatbots feel so fluent and authoritative is the exact same architecture that makes them occasionally, confidently, completely wrong. And no patch has fixed it yet.

What exactly is an AI hallucination?

The term sounds almost poetic. It isn't.

In AI research, a hallucination refers to a plausible but false statement generated by a language model — stated with full confidence, zero caveat, and zero awareness that it's wrong. The model doesn't know it's lying. It can't know. It has no internal fact-checker, no sense of uncertainty, and no way to distinguish between things it 'knows' and things it's extrapolating from statistical patterns.

The OpenAI research team demonstrated this problem concretely. When researchers asked a widely used chatbot for the PhD dissertation title of Adam Tauman Kalai — one of the paper's own authors — the model produced three different answers. All three were wrong. When asked for his birthday, it gave three different dates. Also all wrong. This wasn't an edge case or a trick question. It was a simple factual query about a named academic.

The term 'hallucination' was borrowed from psychology, where it describes perceiving something that isn't there. In AI, it maps surprisingly well: the model perceives a coherent, confident answer where there is actually only uncertainty. Researchers sometimes use the blunter term confabulation — a word from neuroscience describing when brain-damaged patients fill memory gaps with fabricated but sincerely believed stories. That parallel is uncomfortable, and intentional.

Hallucinations show up across modalities. Text models invent fake citations, false historical dates, and non-existent laws. Image-generation models produce anatomically wrong hands, physically impossible shadows, and — in one documented case — a video of Scotland's Glenfinnan Viaduct showing trains running on the wrong side of the track, a second chimney that doesn't exist, and carriages that bend mid-turn. The error type changes. The underlying cause doesn't.

Why does this happen at the architecture level?

This is where the answer gets genuinely surprising. Hallucinations aren't a bug someone forgot to fix. They're a near-inevitable consequence of how language models are constructed.

A large language model learns by processing vast amounts of text — hundreds of billions of words scraped from books, websites, academic papers, forums, and more. During training, it learns one thing above all else: which words are likely to follow which other words, in what context. It becomes extraordinarily good at this. Disturbingly good, actually.

But 'predicting likely next words' and 'retrieving accurate facts' are not the same task. When you ask a language model who invented the telephone, it doesn't query a database. It generates the answer that statistically fits the pattern of how questions like that are answered in its training data. Usually, that produces the right answer. Sometimes it doesn't — and the model has no reliable way to tell the difference.

The problem is compounded by how models are evaluated and rewarded during training. As OpenAI's 2025 paper argued, standard training procedures reward fluency and apparent confidence. A model that says 'I'm not sure' gets penalised in human feedback loops where evaluators prefer helpful, complete-sounding answers. So models learn to guess rather than hedge. They optimise for sounding right, not for being right.

There's also a structural issue called the knowledge cutoff. Models are trained on data up to a certain date, then deployed into a world that keeps changing. Ask about events after the cutoff and the model has no training signal at all — but it still tries to answer, drawing on whatever patterns seem to fit. The result is confident-sounding fiction.

Why can't engineers just fix it?

If you understand why hallucinations happen, the next question is obvious: why hasn't someone patched it?

Several techniques exist to reduce hallucinations, and they work — partially. Retrieval-augmented generation, known as RAG, connects a language model to external databases or live search results before answering. Instead of relying purely on memorised patterns, the model can pull in verified information first. This helps significantly for factual queries. It doesn't eliminate the problem.

Reinforcement learning from human feedback, or RLHF, trains models on ratings from human evaluators who reward accurate, helpful responses and penalise errors. GPT-5 demonstrably produces fewer hallucinations than its predecessors partly for this reason. But as OpenAI acknowledged directly, hallucinations 'remain a fundamental challenge for all large language models.' The improvement is real. The problem isn't solved.

The deeper issue is that truth is hard to define at training scale. Teaching a model to 'be accurate' requires a ground truth to compare against — but training datasets are enormous, diverse, and full of contradictions, opinions, outdated facts, and contested claims. There's no easy way to label 500 billion words as true or false.

There's also a tension between capability and caution. A model trained to say 'I don't know' more often becomes less useful. Users want answers, not uncertainty. Research suggests that users consistently rate confident-sounding AI responses as more helpful — even when those responses are wrong. This creates a feedback loop: the pressure to be useful fights directly against the goal of being accurate.

Some researchers argue that hallucination may be mathematically unavoidable in any system that generalises from patterns rather than retrieving from verified records. That's not a counsel of despair — it's a useful framing. It means the right question isn't 'can we eliminate hallucinations?' but 'how do we build systems that know when they're likely to be wrong?'

Which types of questions trigger hallucinations most?

Not all queries carry equal risk. Understanding the failure patterns makes you a smarter user.

The highest-risk categories are well-documented:

Obscure factual details — specific dates, niche academic citations, minor historical figures, legal statutes. The model has less training signal here and more room to confabulate plausibly.
Questions about named individuals — particularly people who aren't famous enough to dominate the training data. The model will often blend facts from similar people or invent plausible-sounding biographical details.
Recent events — anything close to or after the training cutoff, where the model is essentially guessing from prior patterns.
Precise numerical claims — statistics, study sample sizes, percentages. Models are notoriously prone to generating numbers that feel right without being right.
Legal and medical specifics — where small errors carry serious consequences and where the training data is dense with varied, sometimes contradictory sources.

Lower-risk queries tend to involve widely documented, heavily repeated facts — well-known historical events, basic scientific principles, commonly explained concepts. When the training data contains thousands of consistent sources all saying the same thing, the statistical pull toward the correct answer is strong.

The dangerous middle ground is the confident-sounding answer on a moderately obscure topic. The model has enough training data to pattern-match convincingly, but not enough to nail the details. This is where hallucinations are hardest to detect — because the surrounding context sounds right, even when the specific claim is fabricated. A 2023 study of AI-generated legal citations found a significant proportion of cited cases simply didn't exist, yet the case names, court levels, and legal reasoning surrounding them were entirely plausible.

How should you actually use AI chatbots knowing this?

The answer isn't to stop using them. It's to use them like a brilliant but unreliable research assistant who reads fast, thinks fast, and occasionally makes things up without realising it.

The most practically useful shift is treating AI outputs as a starting point, not a conclusion. For creative tasks, brainstorming, drafting, summarising, and explaining concepts you can independently verify — AI is genuinely powerful and the hallucination risk is manageable. For precise factual claims, citations, legal specifics, or medical information, treat every output as a hypothesis to be checked.

A few concrete strategies that reduce your exposure:

Ask the model to flag uncertainty. Prompting with 'tell me if you're unsure about any of this' doesn't eliminate hallucinations, but it often surfaces hedging language that signals lower-confidence claims.
Request sources, then verify them independently. AI-generated citations are high-risk. Check that the paper, article, or case actually exists before using it.
Cross-reference specific facts. A 30-second Google search on any precise claim — a date, a statistic, a named individual's credentials — is usually enough to catch a confabulation before it causes a problem.
Use retrieval-augmented tools where possible. Products like Perplexity AI or Bing Chat with live search enabled ground responses in real sources, dramatically reducing hallucination risk for factual queries.

The deeper insight is about calibrated trust. The problem with hallucinations isn't just that AI gets things wrong — it's that it gets things wrong while sounding exactly the same as when it gets things right. Building the habit of verification isn't a workaround for a broken tool. It's the correct mental model for any system that reasons by pattern rather than proof.

Hallucinations aren't a temporary flaw waiting for the right software update. They're a structural consequence of building systems that predict language rather than verify truth. That doesn't make AI chatbots useless — it makes them a specific kind of tool, with a specific failure mode you now understand. The smartest users aren't the ones who distrust AI completely. They're the ones who know exactly when to trust it and when to check.

Originally published on SnackIQ

AI Secretly Drinks More Water Than You Think

SnackIQ — Fri, 08 May 2026 08:03:21 +0000

AI water consumption compared to other industries is far more alarming than most people realise. A single large data centre can consume up to 5 million gallons of water per day — equivalent to the daily water use of a town of 10,000 to 50,000 people, according to the Environmental and Energy Study Institute. Researchers at Cornell University estimated that by 2027, AI-related water withdrawals could exceed 6 billion cubic metres annually — roughly equal to New Zealand's entire yearly water consumption. That's not a rounding error. That's a country's worth of water, evaporated to keep silicon chips from melting. And most people using AI assistants have no idea it's happening.

What Actually Happens Inside a Data Centre

Before the numbers make sense, the mechanism has to. And the mechanism is surprisingly old-fashioned.

When you type a prompt into an AI chatbot, your request travels to a data centre — a warehouse packed with thousands of servers running at full tilt. Those chips generate enormous heat. Leave them unchecked, and they fail. So data centres cool them constantly, and the dominant method is evaporative cooling: water is pumped through cooling towers, absorbs heat, and evaporates into the atmosphere. It works brilliantly. It also consumes staggering volumes of fresh water.

AI workloads are particularly punishing on cooling systems. Training a large language model — the kind that powers ChatGPT or Google Gemini — requires sustained, intensive computation over days or weeks. Even inference, the everyday act of generating a response, runs hotter than traditional database queries. More heat means more water. More AI means more heat.

The International Energy Agency has tracked this acceleration closely, finding that global data centre capacity needed to train and run AI models has nearly doubled every five years since 2015. That doubling compounds. What feels like a gradual climb in one decade becomes a vertical wall in the next.

The location of data centres matters enormously too. A facility in a cool, wet climate like Scandinavia can use outside air for cooling — dramatically reducing water draw. The same facility planted in Arizona or central Texas draws heavily on local aquifers, often in areas already under water stress. Geography turns an engineering problem into a geopolitical one.

AI vs Other Industries by the Numbers

Context is everything. AI's water use sounds catastrophic in isolation — but how does it actually stack up against the sectors we already accept as water-hungry?

Sector	Estimated Annual Water Use	Key Driver
Global Agriculture	~2,700 billion cubic metres	Irrigation for crops and livestock
Thermoelectric Power Generation	~580 billion cubic metres	Steam cooling for coal, gas, nuclear plants
Steel Manufacturing	~40 billion cubic metres	Quenching, processing, cooling
Global Data Centres (all computing)	~17–20 billion cubic metres	Server cooling via evaporative towers
AI-Specific Workloads (projected 2027)	~6 billion cubic metres	LLM training and inference cooling
Average human (drinking + sanitation)	~0.0005 cubic metres per day	Basic biological need

On a global scale, AI's water footprint is still a fraction of agriculture's. Researchers at Bryant Research have noted that AI-related consumption may be hundreds of times smaller than the agricultural sector overall. A trillion radishes — an analogy used by tech policy analysts to illustrate agriculture's dominance — still drink far more than every GPU on the planet.

But the comparison isn't quite that simple. Agriculture feeds 8 billion people. AI, at this point, drafts emails and generates images. The efficiency question — water consumed per unit of genuine human value delivered — looks very different depending on what you're measuring.

And the trajectory matters more than the snapshot. Agriculture's water use is relatively stable. AI's is compounding annually.

Where the Pressure Actually Falls

Raw global totals obscure the real story. The damage isn't spread evenly — it's concentrated.

Data Centre Location	Local Water Stress Level	Cooling Method Typically Used	Community Risk
Phoenix, Arizona, USA	Extremely High	Evaporative cooling	Competes with residential and agricultural users
Northern Virginia, USA	Medium	Mixed evaporative and air	High density of centres amplifies cumulative draw
Dublin, Ireland	Low	Predominantly air-cooled	Energy grid strain outweighs water risk
Singapore	High	Chilled water systems	City-state imports most water; highly vulnerable
Stockholm, Sweden	Very Low	Free air cooling (cold climate)	Minimal water risk; near-zero freshwater draw

The pattern is stark. The highest-risk communities are those already living with water scarcity. When a hyperscale data centre moves into a drought-prone region, it doesn't bring its own water — it competes for what's already there. Municipal supplies, agricultural irrigation, and ecological minimum flows all feel the pressure.

This isn't hypothetical. Communities in Arizona, Nevada, and parts of Chile have raised formal objections to data centre developments citing groundwater depletion. The people most affected are rarely the people using AI tools most intensively. That gap — between who benefits and who bears the cost — is where the real ethical weight sits.

Tech Policy Press and other analysts have pointed out that AI's water crisis is structurally a justice issue as much as an environmental one.

How AI's Thirst Compares Per Task

Global totals are one lens. Per-task comparisons are another — and they're more useful for understanding individual responsibility.

Activity	Estimated Water Use	Notes
One ChatGPT conversation (10–50 exchanges)	~500 ml	Estimate based on research published by University of California researchers
Training GPT-3 (one-time)	~700,000 litres	Estimated by researchers studying ML carbon and water costs
Producing 1 kg of beef	~15,000 litres	Well-established lifecycle assessment figure
Manufacturing one smartphone	~13,000 litres	Includes semiconductor fabrication and mining
One load of laundry	~50–75 litres	Standard washing machine cycle
Growing 1 kg of rice	~2,500 litres	FAO standard estimate
One Google search (non-AI)	~0.3 ml	Orders of magnitude below an AI prompt

Researchers at the University of California, Riverside published findings suggesting that generating 100 responses from a large AI model requires roughly half a litre of fresh water — a figure that shocked many readers when it circulated widely in 2023. The number has been debated since, partly because cooling efficiency varies so much by facility and climate.

What's not debated is the direction of travel. As AI becomes embedded in search engines, productivity software, and mobile apps, the per-task cost gets multiplied across billions of daily interactions. The individual number is small. The aggregate is a river.

Compared to a beef burger, a single AI conversation looks trivial. But nobody eats a billion burgers a day. AI systems collectively process queries at that scale — and the volume is still growing.

Can the Industry Actually Fix This

The honest answer: partly, but not enough, and not fast enough.

Several technological approaches genuinely reduce data centre water consumption. Direct-to-chip liquid cooling pipes coolant directly onto processor surfaces, cutting the need for evaporative water towers dramatically. Immersion cooling — submerging servers in engineered dielectric fluid — can eliminate evaporative water loss almost entirely. Microsoft has even experimented with underwater data centres. These approaches work. They are also expensive to retrofit into existing facilities.

Cooling Technology	Water Usage (relative)	Adoption Rate (estimated)	Barrier to Scale
Evaporative cooling towers	High (baseline)	~70% of global centres	Cheap and familiar — incumbent advantage
Air-side economisation	Low–Medium	~20% of centres	Climate-dependent; ineffective in hot regions
Direct-to-chip liquid cooling	Very Low	~5–8% of centres	High upfront capital cost
Full immersion cooling	Near Zero	Under 2% of centres	Complex maintenance; niche expertise required

Beyond hardware, location strategy matters. Building new data centres in cooler climates with low water stress — Iceland, Norway, northern Canada — sidesteps the problem geographically. The International Energy Agency has flagged this as a meaningful policy lever, though it conflicts with latency requirements: cloud services perform better when data centres sit close to their users.

Regulation is the missing piece. Most jurisdictions don't require data centres to disclose water consumption publicly. Without that transparency, market pressure can't do its work. The EU has begun moving toward mandatory environmental disclosures for large facilities, but enforcement timelines stretch years into the future. Meanwhile, the infrastructure keeps expanding.

The sector isn't ignoring the problem. Google, Microsoft, and Meta have all published water stewardship commitments. But commitments written in press releases and efficiency gains measured in engineering reports are two different things. The gap between them is where scrutiny belongs.

AI water consumption compared to other industries looks manageable on a global spreadsheet. It looks very different if you live next to the aquifer a new data centre just claimed. The sector's total draw is still dwarfed by agriculture and power generation — but it's compounding at a rate neither of those industries matched in their early decades. Every technological revolution has had physical costs that arrived before the accounting did. This one is no different. The question is whether the accounting catches up before the wells run dry.

Originally published on SnackIQ