Anubis rarely ever annoys me (I still prefer it over cloudflare’s Mitm) but this specific visit feels almost vindictive. It used half my CPU cores at full blast for three straight minutes.
It seems to be effective since I can’t really “bypass” it with extensions, so AI crawlers probably can’t either, but damn there really should be an option to complete a manual captcha or email the administrators to complain.
As I’m typing this the challenge is still running xD
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 respond with a bad gateway error.
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.
Disagree, that just stops me from using it completely instead of just having to wait a bit
Waiting 3 minutes stops me from using a site. If it’s something I really need I’ll check back in an hour or two, when hopefully it’s not getting hammered; the same for both approaches.
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.