Comment on Tried to login to the arch wiki but was given a 3 minute crypto challenge.
PumaStoleMyBluff@lemmy.world 10 hours ago
The idea is that at individual scales the additional load is ignorable
So uh anyone anyone gonna tell them the idea was wrong? Three minutes is not ignorable.
bountygiver@lemmy.ml 8 hours ago
The difficulty is typically dynamic based on current request load. At this difficulty typically means their server is getting hammered really hard, better this than the server just response with a bad gateway.
PumaStoleMyBluff@lemmy.world 7 hours ago
It would be better to serve a static page saying “the server is getting hammered really hard”, and, if possible, context about the duration of the current event and historical frequency.
kuhli@lemmy.dbzer0.com 5 hours ago
Disagree, that just stops me from using it completely instead of just having to wait a bit
PumaStoleMyBluff@lemmy.world 13 minutes ago
Waiting 3 minutes stops me from using a site.
Funwayguy@lemmy.world 3 hours ago
Less sites are doing that to intentionally avoid tipping off the AIs about thresholds and trigger behaviours. The two main solutions are browser crypto challenges like this, or silently diverting flagged connections to a tar-pit of fake pages. The former is easier to implement but the latter actively sabotages the scraped data.