They ignore robots.txt rules and seem to scrape as quickly and as broadly as possible. Unlike search engines, it doesn't matter to the LLM provider if the website is offline. Unlike search engines, they take steps to be anonymous and difficult to block, including using residential proxy services and other shared IP space.
I try and keep an open data repository online, but it was not designed for this. Cloudflare is hopefully a temporary fix while we redesign backend and frontend components.
The end result is going to be worse for users — slower querying, less flexibility as we primarily expose what we can precalculate, shifting CPU and bandwidth load to the user's device rather than our servers.
For example OpenStreetMap is using nowadays this or equivalents to prevent downtime and/or runaway costs.
Luckily command+shift+t undoes.
What I do not appreciate as well is companies with larger money pool also resorting to and not caring for, for example Dell has the stupidest security check that has disappointed me (a human) enough times one time that I chose to buy a competitors product.
The Russian government being stupid and evil isn't really Cloudflare's problem to solve. Neither is the lack of abuse prevention from VPN providers necessitating the extra challenges for VPN IP blocks. And, now that botnets are the norm, residential IP addresses too.
Obviously, Cloudflare's tools aren't the solution. The web needs to be closed down behind paid or real-identity accounts for websites to ditch these protections. It's only going to get worse from here.
a $10 VPS hosting a static website can trivially serve a thousand pages per second.
I have a few fuckass websites hosted together on the cheapest VPS I could find, and the last time I got an automated alert about downtime was a decade ago.
there is simply no incentive for anyone to ddos a random website.
>The Russian government being stupid and evil isn't really Cloudflare's problem to solve.
didn't imply it was, it was just an observation that everyone uses Cloudflare now.