For the third time in recent memory, CloudFlare has blocked large swaths of niche browsers and their users from accessing web sites that CloudFlare gate-keeps. In the past these issues have been resolved quickly (within a week) and apologies issued with promises to do better:
2024-03-11: Cloudflare checks broken again?
2024-07-08: Cloudflare checks broken yet AGAIN?
2025-01-30: Cloudflare Verification Loop issues
This time around it has been over 6 weeks and CloudFlare has been unable or unwilling to fix the problem on their end, effectively stalling any progress on the matter with various tactics including asking browser developers to sign overarching NDAs:
Re: CloudFlare: summary and status
Some of the affected browsers:
• Pale Moon
• Basilisk
• Waterfox
• Falkon
• SeaMonkey
• Various Firefox ESR flavors
• Thorium (on some systems)
• Ungoogled Chromium
From the main developer of Pale Moon:
Our current situation remains unchanged: CloudFlare is still blocking our access to websites through the challenges, and the captcha/turnstile continues to hang the browser until our watchdog terminates the hung script after which it reloads and hangs again after a short pause (but allowing users to close the tab in that pause, at least). To say that this upsets me is an understatement. Other than deliberate intent or absolute incompetence, I see no reason for this to endure. Neither of those options are very flattering for CloudFlare.
I wish I had better news.
(Score: 2) by looorg on Monday March 17, @08:42PM (2 children)
I thought this had changed a few days after this was mentioned the last time here [1]. But it wasn't there was just some momentary glitch in the matrix that didn't crash things. It went back to endlessly looping and bringing down the entire browser with it. It's been like that ever since.
The only thing I have noticed is that a few sites that did use to use Cloudflare have since changed their settings and are relying less on it. I guess they noticed a somewhat significant drop in traffic or something.
Still it seem petty and stupid and I still don't understand the reason for them implementing it to begin with. But I'm sure some MBA have their reasons.
[1] https://soylentnews.org/article.pl?sid=25/02/07/044225 [soylentnews.org]
(Score: 2) by corey on Monday March 17, @10:05PM (1 child)
Yeah I am also doubting the necessity of this feature. I often get a message saying “making sure you’re a human” For a few seconds before the actual page loads. Is there an actual problem of bots operated by hackers that crawl websites to necessitate this rubbish? I wonder how much of a problem it really is.
I’m only grateful that mostly it’s automatic and not a captcha that asks me to identify all crossings or motorcycles in a bunch of images.
(Score: 2) by looorg on Monday March 17, @10:13PM
That is the one. Or that is how it's supposed to work or how it works in other browsers. It loops for a bit and then it have the display with the checkbox asking if you are human or not. In the looping-browsers that box just never comes up. It stalls. Then it doesn't display the box. Then it either crashes the browser, loops again or something such. It just doesn't stop and displays that box for you to click in and verify that you are human, cause that is apparently what is human -- clicking in boxes.
It's been a while since I saw that one with click all the bikes, crossings, stairs, motorcycles or whatnot. Even in other browsers.