Cloudflare at some point switched to 503 which I hate. It's incorrect. I am considering using 511 (the code for things like WiFi Terms of Service pages).
It's an interestingly unanswered question considering how the HTTP status code RFC is notoriously bloated (see 418 I am a Teapot). And, additionally, Cloudflare is working with Apple to make a new kind of anonymous and instant captcha that involves using your device ID.
@Boyka@josh I don’t have any strong feelings about what’s semantically “correct”, but I would probably copy what Cloudflare is doing for the sake of compatibility. That’s the Fediverse dev mindset.
@Boyka@josh 503 makes sense because if you’re a human you don’t care about the HTTP status code. But if you’re a bot, you’re not getting past that page. So “service unavailable” actually does make perfect sense.
@alex@Boyka@josh I don't think "service unavailable" makes sense here because in fact the service _is_ available but access is being denied for whatever reason
"403 forbidden" seems clear enough to me
"450 Blocked by Windows Parental Controls" would be amusing
of course the page should just clearly state "we think you're a bot" in plain english and at that point it's all sort of irrelevant
in fact you might just return 200 and a static page that explains what's going on