|
|
|
|
|
by folli
1190 days ago
|
|
Yes, I'm not too big of a fan of Google. Plus (I don't really know how it works behind the scenes) the Cloudflare approach is a simple checkmark, so there's no annoying clicking of tiles with motorcycles in it... Any ideas on how a simple proof-of-work could look like, also from the backend side? |
|
The issue with that approach is that slower clients will take longer to solve the challenge, but it just needs to be prohibitely expensive (and slow) for the attacker to spam this, even if they have powerful machines. Botnets can sidestep the issue a bit by distributing computing, but this should still slow them down.
You could also ask for the client's best find after x seconds if it's low-powered, and check that it is reasonable (though that can be gamed). The difficulty can also be increased temporarily if there is a surge of requests.
Maybe we need some kind of "Internet weather forecast" to adjust captca difficulty across websites according to detected botnet activity?