Last month is ancient? Now I really feel old…
You’re right, it’s specific targeting. As you said, it’s not “web standards” or “ancient versions.” Your own post paints a very clear picture of Cloudflare’s targeting, yet you continue to defend them just as rabidly as we’re defending our browsers of choice.
First, hCaptcha has nothing to do with this and your bringing it up is disingenuous at best.
Second, I have NEVER had an issue solving hCaptcha with Pale Moon that wasn’t self-inflicted with an addon. Even reCaptcha works in a clean profile in Pale Moon. This latest “incompatibility” is SPECIFIC TARGETING of the Pale Moon browser or its render engine by Cloudflare. As you pointed out, all of those other “ancient” browsers pass while Pale Moon fails. If it’s not specific targeting of Pale Moon or its render engine specifically, please tell us what it is about that browser that makes it fail or get us in touch with someone who can.
We’re only here because of a lack of support by an unresponsive company that is currently engaged in what is effectively a man-in-the-middle denial-of-service attack on a large chunk of the internet. I would much rather be dealing with Cloudflare engineers in their support ticketing system where my issue could actually get resolved. Instead I’m here feeding a troll because I seem to have nothing better to do with my time.
An action is either accidental or purposeful. Cloudflare knows about this issue and has not corrected it, therefore it is purposeful. A purposeful action with a negative outcome is malicious. Therefore Cloudflare’s action is malicious. That is a statement of fact and stands as a fact until you (or someone else) can present clear evidence that Cloudflare either doesn’t know this is happening or is currently making a good faith effort to correct the issue.
I don’t believe Cloudflare has so far done anything that is actually criminal, regardless of how much we all wish what Cloudflare is doing actually was criminal. So, yes, I agree, “criminal” to too strong of a word at this point.
As you can see this is a genuine issue that is impacting lots of users, so let’s get the issue resolved then!
I was working with @cloonan , then you came in with your negativity and the thread devolved from there. You’ve so far made every attempt to derail this thread and absolutely no attempt whatsoever to constructively work toward a solution. (“Use a different browser” is NOT a solution.) I have asked repeatedly for contact information such that I could take this issue to a more appropriate place and have yet to receive it. (I would accept having said contact information handed to @moonchild so that he can modify the browser so it passes the checks, but that hasn’t happened either as far as I’m aware. I’d actually prefer that as everyone would benefit.) You have failed to respond to any section of my posts where I call out inconsistencies in your posts. (For example, you have yet to tell me how sending the native user agent, which makes no reference to Firefox, is “spoofing” the user agent. You have yet to tell me why Chromium including Safari in its user agent isn’t spoofing and why it’s allowed when Pale Moon including Firefox is not.)
Based on the preponderance of the evidence of various forum threads, Cloudflare is specifically targeting Pale Moon or the specific feature-level of the render engine it uses. You appear to be running interference for Cloudflare on this forum, possibly in an attempt to get a mod to close the thread. (Which would likely just get re-created by someone else now that there are a number of people watching it. Streisand Effect anyone?) I don’t know why all of this is happening, but it is. The only thing we want is for Cloudflare to stop attacking us, or, at the very least, tell us why we’re being attacked and what we did to justify such an attack.