惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

L
LangChain Blog
AWS News Blog
AWS News Blog
Last Week in AI
Last Week in AI
宝玉的分享
宝玉的分享
The Cloudflare Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 三生石上(FineUI控件)
腾讯CDC
Apple Machine Learning Research
Apple Machine Learning Research
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
人人都是产品经理
人人都是产品经理
WordPress大学
WordPress大学
爱范儿
爱范儿
IT之家
IT之家
博客园 - 叶小钗
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
S
SegmentFault 最新的问题
L
Lohrmann on Cybersecurity
Scott Helme
Scott Helme
G
GRAHAM CLULEY
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
美团技术团队
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
Visual Studio Blog
博客园 - 聂微东
有赞技术团队
有赞技术团队
J
Java Code Geeks
小众软件
小众软件
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
V
V2EX
The Last Watchdog
The Last Watchdog
S
Securelist
博客园 - Franky
罗磊的独立博客
阮一峰的网络日志
阮一峰的网络日志
AI
AI
雷峰网
雷峰网
博客园 - 司徒正美
L
LINUX DO - 热门话题
月光博客
月光博客
大猫的无限游戏
大猫的无限游戏
Hugging Face - Blog
Hugging Face - Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
L
LINUX DO - 最新话题
TaoSecurity Blog
TaoSecurity Blog
Cisco Talos Blog
Cisco Talos Blog
K
Kaspersky official blog
H
Hacker News: Front Page
量子位
Latest news
Latest news

Pierce Freeman

A browser for agents | Pierce Freeman The grey market of podcast appearances The way I travel | Pierce Freeman Fixing slow AWS uploads | Pierce Freeman Local tools should still use vaults We solved scratch content first Starting a podcast in 2025 Being late but still being early Automating our home video imports Adding my parents to tailscale A deep dive on agent sandboxes Language servers for AI | Pierce Freeman My simple home podcast studio We need centralized infrastructure | Pierce Freeman Coercing agents to follow conventions using AST validation My unified theory of social selling My personal backup strategy | Pierce Freeman July updates to the homelab How the KV Cache works httpx is the right way to do web requests in Python Reputation is becoming everything | Pierce Freeman Building a (kind of) invisible mac app Updated knowledge in language models Making an ascii animation | Pierce Freeman How speculative decoding works | Pierce Freeman Under the hood of Claude Code Doing things because they're easy, not hard Speeding up sideeffects with JIT in mountaineer Firehot for hot reloading in Python Misadventures in Python hot reloading How text diffusion works | Pierce Freeman The tenacity of modern LLMs The ergonomics of rails | Pierce Freeman How language servers work | Pierce Freeman Just add eggs | Pierce Freeman Unfortunately SEO still matters | Pierce Freeman Setting up Input Leap | Pierce Freeman Checking in on Waymo | Pierce Freeman The react revolution | Pierce Freeman Speeding up many small transfers to a unifi nas Quick notes on swift libraries AI engineering is a different animal San Francisco | Pierce Freeman Debugging a mountaineer rendering segfault Local network config on macOS Building our home network | Pierce Freeman Introducing Envelope.dev | Pierce Freeman Legacy code and AI copilots Typehinting from day-zero | Pierce Freeman Generating database migrations with acyclic graphs Lofoten | Pierce Freeman Mountaineer v0.1: Webapps in Python and React Constraining LLM Outputs | Pierce Freeman Passthrough above all | Pierce Freeman Accuracy in kudos | Pierce Freeman How quick we are to adapt The curious case of LM repetition Costa Rica | Pierce Freeman Debugging chrome extensions with system-level logging Speeding up runpod | Pierce Freeman Inline footnotes with html templates Parsing Common Crawl in a day for $60 An era of rich CLI All or nothing with remote work The Next 10 Years | Pierce Freeman Adding wheels to flash-attention | Pierce Freeman LLMs as interdisciplinary agents | Pierce Freeman New Zealand | Pierce Freeman Representations in autoregressive models | Pierce Freeman Let's talk about Siri | Pierce Freeman Minimum viable public infrastructure | Pierce Freeman Reasoning vs. Memorization in LLMs Automatically migrate enums in alembic Greater sequence lengths will set us free On learning to ski | Pierce Freeman Dolomites | Pierce Freeman Using grpc with node and typescript Opportunity years | Pierce Freeman Buzzword peaks and valleys | Pierce Freeman Buenos Aires | Pierce Freeman Network routing interaction on MacOS Independent work: November recap | Pierce Freeman Debugging slow pytorch training performance The provenance of copy and paste Debugging tips for neural network training Patagonia | Pierce Freeman Santiago | Pierce Freeman My 2022 digital travel kit AWS vs GCP - GPU Availability V2 Independent work: October recap | Pierce Freeman Planning Patagonia | Pierce Freeman Relationship modeling | Pierce Freeman The power of status updates A new chapter | Pierce Freeman Give my library a coffee shop AWS vs GCP - GPU Availability V1 Switzerland | Pierce Freeman Headfull browsers beat headless | Pierce Freeman Webcrawling tradeoffs | Pierce Freeman Copenhagen | Pierce Freeman
The futility of human-only web requirements
2025-06-01 · via Pierce Freeman

There have long been only three abstraction layers to the Web:

  • A visual user interface for the average user
  • Dom markup (aria tags) for accessibility software
  • APIs for machine code

Into this mix comes a fourth. AI Agents are coming for research, they're coming for job hunting, they're even coming for shopping.

We're still locked into a mental model that all bots on the web are bad. They DDoS sites, they scrape data, or they facilitate scalping limited inventory and driving prices higher. Most webmasters tolerate search engine bots because of the additional traffic from being listed in the search results. Without that benefits, I'm inclined to say they would hate all bots categorically.

They sure try to ban them already.

  • TicketMaster's response to ticket scalping? Try to ban the bots.
  • Reddit's response to authenticity? Try to ban the bots.
  • Yelp's response to synthetic reviews? Try to ban the bots.

The list goes on. In response to anti-bot sentiment, a huge secondary industry has emerged to try and protect websites: ReCaptcha, Cloudflare, Fingerprint.js. These anti-bot defenses all rely on detecting the specific markers that make a bot non-human: the speed of navigation, being run in a headless context, only navigating via key commands. If you have a dataset that's big enough it's actually pretty easy to build a model that separate humans from bots. They're usually linearly separable interaction patterns.1

As more AI Agents come online, I remain convinced that we're thinking about this problem wrong. The main thing that product designers should care about is how their end users engage with what they're selling. Ads distorted this model by letting companies "sell" eyeballs - so unless people are actually engaging with their site themselves, they're losing out.

But - dare I say - most companies have value that their direct customers would actually be willing to pay for. They should be asking themselves how real people2 can actually benefit from the use of their site and products, whether or not there's an AI Agent being used as an intermediary.

Business model is the key question. And one question removed is how to execute that business model via code.

Anti-bot protections can't help your bad business models

Take Ticketmaster. Are bots waiting in a queue the problem? Not really. The problem is they'll let anyone with a credit card sign up and buy a (typically) unlimited amount of tickets. So if you're faster to the initial page or can spam a queue with your own delegates, you're necessarily at an advantage. The only way to really combat that? Make people do KYC validation of their drivers license before they can get into the queue in the first place. One ID is one entry into the ticket lottery. That's it.

Take Reddit. Are bots engaging or posting content the issue? It definitely impacts some implicit notion of "authenticity" - but if a bot posts a fire meme versus an anon, on some level who cares. What people really care about are lies about personal experience. If there's a collection of strong recommendations for a restaurant no one has gone to, the value of communities as a vetted space evaporates. Blue-checkmark reddit profiles. 95% of the problem is solved. And then if I use a delegated bot to farm engagement for my account, I have to personally stand behind everything it says.3

We're trying so hard to combat bots. But at what cost? And at what value?

Caught in the collateral

Here's the thing about false positives: they're not edge cases anymore. As bots get better at evading detection, anti-bot detectors have to up their sensitivity and necessarily catch more people in the cross hairs.

The irony is thick. In trying to preserve the "human" web, we've made it hostile to actual humans who don't browse in the exact prescribed manner. It's like a restaurant installing a door so narrow that only average-sized people can enter, then claiming they're protecting the dining experience.

And for what? The serious bad actors - the scalpers, the data thieves, the DDoS networks - they've already moved past your defenses. They're running full browser instances on residential proxies with ML-generated mouse movements that are more "human" than most humans. Your CAPTCHA isn't stopping them. It's stopping my grandmother from buying concert tickets.

The arms race nobody wins

Every new anti-bot measure follows a predictable lifecycle:

  1. Company deploys new detection method (browser fingerprinting!)
  2. Bot developers reverse engineer it (spoofed fingerprints!)
  3. Detection gets more aggressive (track mouse movements!)
  4. Bots get more sophisticated (AI-generated movements!)
  5. Real users suffer (why is this site so slow?)
  6. Repeat until bankruptcy or acquisition

We've created an entire shadow economy of bot developers, anti-bot vendors, and consultants all feeding off this dysfunction. Cloudflare makes bank. Scraping-as-a-service startups proliferate. Meanwhile, the actual problem - preventing abuse while serving customers - remains unsolved.

The truth nobody wants to admit? The bot developers are usually smarter and more motivated than the defenders. They have clear economic incentives. They iterate faster. And they only need to win once, while defenders need to win every time.

If you're not good at a game, the obvious advice is train harder and become better. Train until you win. Maybe here we should just pick up our ball and go home.

When eyeballs stop mattering

The real crisis isn't bots. It's that the entire attention economy is built on a lie. We've been monetizing engagement as if a pageview from a bot, a misclick from a human, and genuine interest are equivalent. They're not, and AI agents are about to make this painfully obvious.

When every user has an AI assistant pre-screening content, what happens to your carefully crafted engagement loops? When agents can skip your ads, ignore your dark patterns, and extract exactly what the user wants? The jig is up. You've just got to build valuable shit and get it to people (and machines) in a way that people are willing to pay for.

The web is about the change dramatically. It's about to kill some businesses and reinvent others. Minimally it's going to force them back to the brainstorming table:

  • What actual value do we provide?
  • Would someone pay for this if we couldn't force them to watch ads?
  • How do we serve the human at the end of the agent chain?

The answer isn't to fight the agents. It's to build something worth paying for, whether the payment comes from a human or a digital representative.

Or we could just legislate this...

Or maybe ads get their way. Maybe they say human eyeballs need to be here to stay. If so I'm guessing they're going to turn to regulation with some teeth.

The TCPA didn't try to detect whether a call was automated - it just made unsolicited automated calls illegal. Charge up to $1,500 per violation and now there's some money on the table. Guess what? The spam dropped dramatically. Not because it became technically impossible, but because most actors didn't want to risk massive fines.

We could do the same for AI-generated content:

  • Require disclosure when content is AI-generated
  • Ban unsolicited AI outreach without explicit consent
  • Set statutory damages high enough that violation isn't worth it

The beauty of this approach? It sidesteps the entire technical arms race. You don't need perfect bot detection if running an undisclosed bot risks a $10,000 fine per post. Most bad actors are rational economic players - make the penalties exceed the profits and watch the behavior change.

Sure, some offshore scammers won't care. But the vast majority of bot activity comes from businesses trying to game the system while maintaining plausible legitimacy. They'll comply because they have assets to lose and reputations to protect.

Either way, whether business models change or laws evolve, the human-only web as we know it is dead. I think it's high time to just admit that and stop the perennial cat and mouse. The mouse won. Go home Tom.

  1. And yes, you can train models to emulate humans. I've done a lot of that. But 99% of bots are too lazy to try so you can filter them out without much trouble. And even the best simulation models are limited by your feature choice and dataset. With a big enough ground truth (where centralized anti-bot platforms are necessarily at an advantage) you can probably build an even better detection model. It's a real world GAN in action. ↩

  2. Perhaps at the end of some lengthy agent value chain. ↩

  3. One of the reasons why I use my full profile on all social is because I want my identity to stand behind my claims. ↩