You try to open a simple open-source repository on Codeberg, and instead of code, you get a cold, white screen: “Access Denied – Suspected AI bot.”
Not a bot. Just a human who wanted to read a README.
You switch your user-agent to pretend you’re a browser, and it works for a while. Then the ban hammer falls again. The machines are winning, but not in the way you think.
Welcome to the absurd new reality of the internet: the people who built the open web are now its most aggressive gatekeepers.
And the irony is so thick you could cut it with a right-click.
Just four years ago, the same crowd that now blocks AI scrapers with Cloudflare and rate limits was laughing at NFT bagholders. “Right click save as,” they mocked, pointing out that digital ownership is a joke when you can just copy the JPEG. “You wouldn’t download a car” was the punchline.
Fast forward to 2024. That same developer community is now deploying anti-bot scripts that prevent you from downloading their code. They’ve built digital scarcity—not for NFTs, but for their own content. And the justification? “AI is scraping our work.”
But here’s the punchline they didn’t see coming: the user who gets locked out isn’t an AI. It’s you.
It’s me, reading a technical blog. It’s a student trying to clone a repo. It’s a journalist verifying a claim. The machines can still get through with clever headers and proxy farms, but the humans—the real humans—are the ones getting denied.
This isn’t just a technical problem. It’s a moral whiplash that exposes a deep contradiction in the open-source and developer communities. We championed an open web, then we built the walled gardens. We mocked digital ownership, then we invented our own form of it—call it “access control based on good behavior.”
And the worst part? The anti-AI arms race is escalating. Every new block spawns a new bypass. Every bypass spawns a stricter block. The arms race doesn’t hurt the bots—it hurts the humans who just want to read a damn article.
The internet’s open architecture is being dismantled by the very people who claimed to love it most.
We need to ask ourselves: who are we really blocking? The machines? Or ourselves? Because at this rate, the only thing we’re going to save is our own hypocrisy.
FAQ
Q: Isn't blocking AI scraping necessary to protect content creators?
A: Yes, content creators deserve protection from wholesale scraping. But the blunt tools being used—IP bans, aggressive CAPTCHAs, user-agent checks—don't just block bots. They block humans. And the irony is that the same people who mocked digital ownership are now enforcing a form of it. The solution should be smarter, not more walls.
Q: What does this mean for the average internet user?
A: It means more frustration. You'll get 'Access Denied' pages on sites you used to browse freely. You'll be forced to solve CAPTCHAs to read a blog post. And eventually, the open web will fragment into a patchwork of gated communities where only humans with perfect browser fingerprints can enter. The 'you' in 'you wouldn't download a car' might soon be the one locked out of the garage.
Q: Isn't this just a necessary evil in the fight against AI?
A: Calling it a 'necessary evil' ignores the fact that the evil is largely self-inflicted. The same community that built the open web on trust and sharing is now using anti-patterns from the DRM era. This isn't a defense—it's a panic reaction. The real necessary evil would be to admit that you can't fight AI scraping by recreating the walled gardens you once despised.