They don't need to shut off Anubis, they just need to configure it beyond the defaults. If they turned on the meta-refresh based challenge then all browsers could access it while still keeping most of the bots away. But few people ever configure these things and just accept the broken defaults.

With the current broken default config my browser can't even run the JS challenge due to it using unsupported bleeding edge JS features.

▲

xena 16 hours ago | parent [-]

Hi, can you please paste the error message you get? This should be using features that are supported widely as of 2022 and I regularly test on Firefox LTS.

	▲	cpmsmith 11 hours ago \| parent [-]
		I'm just getting "invalid response." in a 500 response from the `anubis/api/pass-challenge` endpoint – weirdly, when I added breakpoints and stepped through the code myself, it worked, but if I load again, I get the error. Maybe there's a timing component? (Firefox stable)