How do they get overloaded? Is the website too slow? I have a quite big wiki online and barely see any impact from bots.
We can't have nice things because of AI scrapers
51–60 of 279 posts
Re: We can't have nice things because of AI scrapers
#52Resurfacing a proposal I put out on llms-txt: https://github.com/AnswerDotAI/llms-txt/issues/88 We should add optional `tips` addresses in llms.txt files. We're also working on enabling and solving this at Grove.city. Human Agent Human Tips don't account for all the edge cases, but they're a necessary and happy neutral medium. Moving fast. Would love to share more with the community. Wrote about it here: https://x.co…
Though if LLMs are willingly ignoring robots.txt, often hiding themselves or using third party scraped data- are they going to pay?
Re: We can't have nice things because of AI scrapers
#53How do they get overloaded? Is the website too slow? I have a quite big wiki online and barely see any impact from bots.
Re: We can't have nice things because of AI scrapers
#54How do they get overloaded? Is the website too slow? I have a quite big wiki online and barely see any impact from bots.
Re: We can't have nice things because of AI scrapers
#55How do they get overloaded? Is the website too slow? I have a quite big wiki online and barely see any impact from bots.
Many of them don't even self-identify and end up scraping with shrouded user-agents or via bot-farms. I've had to block entire ASNs just to tone it down. It also hurts good-faith actors who genuinely want to build on top of our APIs because I have to block some cloud providers.
I would guess that I'm getting anywhere from 10-25 AI bot requests (maybe more) per real user request - and at scale that ends up being quite a lot. I route bot traffic to separate pods just so it doesn't hinder my real users' experience[0]. Keep in mind that they're hitting deeply cold links so caching doesn't do a whole lot here.
[0] this was more of a fun experiment than anything explicitly necessary, but it's proven useful in ways I didn't anticipate
Re: We can't have nice things because of AI scrapers
#56Re: We can't have nice things because of AI scrapers
#57"The malefactor behind this attack could just clone the whole SQLite source repository and search all the content on his own machine, at his leisure. But no: Being evil, the culprit feels compelled to ruin it for everyone else. This is why you don't get to keep nice things...."
Re: We can't have nice things because of AI scrapers
#58Earlier quoted context omitted.
> They won't believe a random site when it says "Look, stop hitting our API, you can pick all of this data in one go, over in this gzipped tar file." What mechanism does a site have for doing that? I don't see anything in robots.txt standard about being able to set priority but I could be missing something.
It’s not great, but you could add it to the body of a 429 response.
Re: We can't have nice things because of AI scrapers
#59Re: We can't have nice things because of AI scrapers
#60I actually deleted my web site early 2025 and removed the A record from DNS because of AI scraper traffic. It had been up for 22 years. Nothing important or particularly useful on it but it's an indicator of the times.