With the current broken default config my browser can't even run the JS challenge due to it using unsupported bleeding edge JS features.
[12:03:18.699] GET https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/13ce36fef98a3f4... [HTTP/1.1 200 OK 227ms] [12:03:19.483] GET https://code.ffmpeg.org/.within.website/x/xess/xess.min.css?... [HTTP/1.1 200 OK 611ms] [12:03:19.485] GET https://code.ffmpeg.org/.within.website/x/cmd/anubis/static/... [HTTP/1.1 200 OK 839ms] [12:03:19.486] GET https://code.ffmpeg.org/.within.website/x/cmd/anubis/static/... [HTTP/1.1 200 OK 391ms] [12:03:19.487] GET https://code.ffmpeg.org/.within.website/x/cmd/anubis/static/... [HTTP/1.1 200 OK 368ms]
For clarification I am using a version of Firefox from about 2015. But this version of Firefox does work with the meta-refresh based Anubis option.
https://web.archive.org/web/20250813104007/https://code.ffmp...
You can read it on one of these without having to pass that specific bot check
It's up to the site admin to configure it that way, but it's possible some IP ranges/user agents are more often used by bots and therefore have an increased weight.
For old browsers there's also an option to use meta refresh instead of JS (https://anubis.techaro.lol/docs/admin/configuration/challeng...) but that's quite a recent addition and not enabled by default.
I'm currently roaming in Finland with a Spanish SIM so would have expected the opposite in that case.
This page loaded pretty much instantly (certainly in the time it took to switch to the background tab I loaded in). But then ffmpeg is written by old school engineers with old school ways of working. Their social media accounts are a hilarity of trolling worthy of slashdot in its peak.