Earlier quoted context omitted.
Which is trivially bypassed by an actual implementation of the proof of work in non-javascript, rendering it absolutely useless. The website is approximately 3800x times slower than native code, and hundreds of thousands of times slower than the CUDA kernel claude wrote. The "proof of work" is just non existent at that point, they're solved in milliseconds for what would take the browser version 10 minutes or more, i…
But the people you're defending against don't do that. They also don't load CSS but for some reason the security theater PoW won the mindshare.
A year of fighting scrapers on my 1.5 million-page website
151–160 of 453 posts
Re: A year of fighting scrapers on my 1.5 million-page website
#152Can someone help me understand the underlying motivation behind this? It makes sense that some crawlers, in the style of Google, would want to index the entire internet. But what is the point of the same crawler re-fetching a page they already fetched an hour ago? Or possibly all this traffic is just independent entities, each trying to cache the internet? The scale of bot traffic makes this seem unlikely. What's the…
Re: A year of fighting scrapers on my 1.5 million-page website
#153Earlier quoted context omitted.
People tried this in 2013 or so, there's no point to it. Doing proof of work in javascript in a browser is so crushingly, pointlessly slow that there's no value at all. Some browsers also intentionally detect attempts to do proof of work and attempt to block it entirely.
> Some browsers also intentionally detect attempts to do proof of work and attempt to block it entirely. Then they'd be blocking themselves from the website.
To help you combat these unwelcome scripts, we’ve partnered with Disconnect and compiled lists of domains that serve cryptomining scripts so you can block them directly through Firefox. When you download Firefox, tracking protection is enabled by default, blocking known cryptominers.Re: A year of fighting scrapers on my 1.5 million-page website
#154The worrying thing here is that so many people accepted outsourcing the decision on who can see their website to a large company (Cloudflare). If the company decides that a certain user should not see the website, the user will not see the website, and no one will know about it, and the user will have no recourse. That is not the open web that I would like to see. A second side effect of a knee-jerk reaction to bots…
why you blaming cloudflare that try to solve botting issue and not the Botters ??? you literally can turn off cloudflare and use your own solution
Re: A year of fighting scrapers on my 1.5 million-page website
#155The worrying thing here is that so many people accepted outsourcing the decision on who can see their website to a large company (Cloudflare). If the company decides that a certain user should not see the website, the user will not see the website, and no one will know about it, and the user will have no recourse. That is not the open web that I would like to see. A second side effect of a knee-jerk reaction to bots…
> I wanted the information and I have no way of getting at it without investing my own time and effort in going to your website. I think you've hit the nail on the head here. I think that's a big reason why people want to ban bots.
Re: A year of fighting scrapers on my 1.5 million-page website
#156I'm in a similar boat. Probably 99.999% is bots. I have nearly 1m unique "visitors" according to cloudflare and my real users are in the dozens a day. That being said, I love the open internet and am holding on to keeping as much open as I can.
But what do these bots gain from this?
Re: A year of fighting scrapers on my 1.5 million-page website
#157Re: A year of fighting scrapers on my 1.5 million-page website
#158The worrying thing here is that so many people accepted outsourcing the decision on who can see their website to a large company (Cloudflare). If the company decides that a certain user should not see the website, the user will not see the website, and no one will know about it, and the user will have no recourse. That is not the open web that I would like to see. A second side effect of a knee-jerk reaction to bots…
>That is not the open web that I would like to see. Cloudflare is opt-in so I don't see that being an issue (yet).
Re: A year of fighting scrapers on my 1.5 million-page website
#159Earlier quoted context omitted.
Static files on literally any hardware from the last 15 years on modern server software simply won't get cooked by bots. The network switch will bottleneck you before the server will. Your ephemeral port range will run out before the server will.
Bandwidth is still not free, if you cloud host. I had a client ask me to look into why their bill spiked 5x (admittedly not by much - from a few dollars to tens). They run a static site, and it turned out someone had inadvertently replaced an image with a massive uncompressed photo. Every unique visitor was caching O(25MB) when they loaded the homepage. Also funny because now everyone has 100Mb+ internet, nobody noti…
Re: A year of fighting scrapers on my 1.5 million-page website
#160Is there any cheap way to run personal websites without getting cooked by bots these days, degrading the performance? A $5/month VPS won't cut it anymore.