iFixit CEO Kyle Wiens calls out Anthropic for disruptive crawling
twitter.com
twitter.com
https://blog.cloudflare.com/declaring-your-aindependence-blo...
Further, on the content scraping side, aren't there better ways to determine when to re-scrape so you're not completely overloading servers of folks who don't have easily cache-able static content? Are "HTTP/1.1 304 Not Modified" header responses too difficult to implement or honor? Seems like failures on both sides are what leads to these situations.
Assuming they're literally getting hit "a million times in 24 hours", wouldn't it still cost bandwidth? Also, perhaps iFixit doesn't have such traffic in their past so they didn't bother optimzing prematurely.
I feel the blame mostly falls on Anthropic not being considerate when they scrape other people's content.
That's certainly a fair assumption. I haven't looked into it in any detail. Is IFixit sending appropriate cache headers or is Anthropic just ignoring them? I don't know. But at some point, your caching strategy and your ability to respond to spikes in demand is your own problem. We live in reality, and in reality you can't really control who is hitting your website when. Sure, it would be nice if they respected your cache control policies, but what are you doing when you know they won't? I'll refer back to my previous statement. It's totally understandable when someone who didn't expect ever HN levels of attentions to be overwhelmed. But if you're a site as large and respected as IFixit, you've got to do better than the "unwashed masses".
They are no strangers to bursty traffic. We would get insane bursts of traffic many, many times greater than typical wherever a teardown of a new iDevice was published shortly after release.
If Kyle and the devops folks there are noticing it, it’s definitely disruptive behavior.
On a smaller site, it can absolutely be brutal. I worked on a site where literally 2/3 of requests were bots and a lot of those were dynamically constructed pages that are/were harder to cache. In the end, switching to a supplemental search database helped significantly, but it doesn't mean that an aggressive bot is an okay thing.