Rationale:
- The db currently tracks “
has_captcha”. Cloudflare influences that regardless of whether the site is itself configured to push a CAPTCHA. - The db currently tracks “
open_registrations”. The degree of openness depends on whether a node is on Cloudflare, regardless of how the software is configured. - Checking for Cloudflare is free. That is, no extra connections are needed. It’s simply a matter of checking for the presence of
CF-RAYin the http headers on existing fetches. - The mission purpose of fediseer is to facilitate trust assessment. The use of Cloudflare is a significant factor in that regard.
Down? Run smoothly
It’s still down for me. Just times out. So I have no idea what you propose.
Anyway, I don’t imagine how a workaround would be possible. The dataset is missing the data. If I have to scrape for the data myself, it defeats the point of a public dataset. I could write in my code a Cloudflare check, but that doesn’t help anyone else using the fediseer dataset.
Then the only thing that comes to mind is that your IP address must be on a Crowdsec ban list.
https://codeberg.org/Tealk/fediseer-hesitations-cloudflare