Most web proof-of-work stuff has worked because it breaks the normal flow and the typical scraper is supremely dumb, not because of the proof of work, which has largely been a total red herring.
Most web proof-of-work stuff has worked because it breaks the normal flow and the typical scraper is supremely dumb, not because of the proof of work, which has largely been a total red herring.
You don't need to win. You just need to tip the scales a little bit. Even two stage request response of PoW would dissuade some scraping.
> if you want to require an attacker to burn one second of computation time, some cheap smartphone user will now be stuck for five minutes.
I don't want attacker to spend 1 second per request. I want them spend 10 ms per each of their millions of requests. You don't hit them by being request hard. You hit them by making them pay even if just a little bit for each inefficient action they take.
> Most web proof-of-work stuff has worked because it breaks the normal flow and the typical scraper is supremely dumb, not because of the proof of work, which has largely been a total red herring.
It's not really important how you win. It's important to have a control over your hosting costs in this brave new world.
For one, you can make PoW progressive based on the number of requests you've encountered from the same IP address. This does hurt users behind NAT so it's not ideal, but it might be time we moved past NAT.
Secondly, 5 seconds is a lot but not unheard of; you could start PoW in the first lines of your html and load the rest of the assets while you're otherwise busy burning cpu time. 20ms quickly adds up at the scale scrapers operate. Which, according to cloudflare is > 50% of web requests.
Residential proxies are a whitewashed name for botnets, mr consultant.