Well, this time it lasted less than half a month.
Edit: i got through after many page reloads and self-restarts of check. Which means that number of CF cdn server serve version that doesn't work for us.




I think its more likely they don't want to waste much energy in supporting Pale Moon.Night Wing wrote: ↑2026-04-20, 17:40In my opinion Cloudflare does not want to support Pale Moon. This is the short of it.

They are supposed to speak directly with @Moonchild this week and Cloudflare's rep claims that they are trying to fix things with respect to Pale Moon longer term, so let's see if anything good comes of it. I'm forever hopeful. Certainly they responded faster this time around and implemented a temporary fix faster than when it happened last spring, even if their response time still hasn't been perfect.frostknight wrote: ↑2026-04-21, 02:40I think its more likely they don't want to waste much energy in supporting Pale Moon.Night Wing wrote: ↑2026-04-20, 17:40In my opinion Cloudflare does not want to support Pale Moon. This is the short of it.
They want to use the least energy possible to support Pale Moon so they can appear like they don't have favorites.


I have a meeting planned this afternoon my time to discuss things.
Yes and this is the problem with their own "success": by being used on many more websites, their compatibility with browsers has to extend further. They cannot continue to claim nothing outside of Blink/Gecko/webkit exists when it impacts a large portion of the web as it is now. Certainly not engines that are actively developed and maintained.andyprough wrote: ↑2026-04-21, 03:41My bigger problem is that I am now running into Cloudflare turnstiles all the time and even if they don't stop Pale Moon they slow all web browsing to a crawl compared to just a few years ago.

...and their tool needs to become faster and more reliable.

How has that meeting gone?

It was mostly me filling in the new folks (since, surprise surprise, they had a change of RPs in the last year for this part of CloudFlare, so I'm sure most of what was promised wasn't communicated forward... at least it explained the total communications breakdown) with background around Goanna and its separate nature from gecko/blink/etc., the impact the blocking has had on our numbers, and that we can't have some opaque eyes-only secret handshake thing with CF because we're fully open source, and bot devs would happily just copy that and get a free pass.

Do you think this meeting will finally put an end to Cloudflare breaking on UXP (or at the very least, make the breakages a lot less impactful), or do you think it's just another thing that'll make Cloudflare look good in the eyes of the public but in reality nothing happens?Moonchild wrote: ↑2026-04-22, 04:57It was mostly me filling in the new folks (since surprise surprise they had a change of RPs in the last year for this part of CloudFlare, so I'm sure most of what was promised wasn't communicated forward...) with background around Goanna and its separate nature from gecko/blink/etc., the impact the blocking has had on our numbers, and that we can't have some opaque eyes only secret handshake thing with CF because we're fully open source, and bot devs would happily just copy that and get a free pass.
Oh and I did stress their captcha is the only one with severe problems for us, unlike recaltcha, hcaptcha, anubis, etc. Irony being the biggest is the worst

It's a first step. No concrete commitments were made and it was just to map out the general area and what should be done.ownedbywuigi wrote: ↑2026-04-22, 06:38Do you think this meeting will finally put an end to Cloudflare breaking on UXP

If there is a followup meeting, can you ask them if we can have a semi-public channel of communication with them for other browsers, because I almost guarantee we are not the only browser having issues with this, and we're only lucky to have a channel of communication with them AT ALL.Moonchild wrote: ↑2026-04-22, 07:23I'm hopeful that we'll have a better channel of communication going forward and that this kind of real damage is preventedownedbywuigi wrote: ↑2026-04-22, 06:38Do you think this meeting will finally put an end to Cloudflare breaking on UXP

At least you are getting to know new peopleMoonchild wrote: ↑2026-04-22, 04:57It was mostly me filling in the new folks (since, surprise surprise, they had a change of RPs in the last year for this part of CloudFlare, so I'm sure most of what was promised wasn't communicated forward... at least it explained the total communications breakdown

I have been using PM since Jan 2011, my reason is, as you mentioned, "full customization".One question they asked that I didn't expect was "Why do people use Pale Moon?" -- I answered that as best I could since I obviously don't know to what extent each of you has one reason or another, but it'd likely be a mix of project philosophy, trust, technological reasons and focus on full customization.

I use Goanna based browsers on the daily because well, it's the engine that sucks the least, to be fair.Moonchild wrote: ↑2026-04-22, 04:57One question they asked that I didn't expect was "Why do people use Pale Moon?" -- I answered that as best I could since I obviously don't know to what extent each of you has one reason or another, but it'd likely be a mix of project philosophy, trust, technological reasons and focus on full customization.

Care to elaborate on this? It might be relevant, as far as captchas in general are concerned in this thread, to note that Xcancel’s captchas have lately been a looping failure in the Gecko-based browser (Waterfox) I have tried as well as Pale Moon, causing me to return to entering the addresses for scriptless verification ( https://xcancel.com/fumo becomes https://xcancel.com/verify/index?url=/fumo ) manually. Since this is common to Gecko as well as Goanna, I decided against making a thread about the JS-based captcha’s misbehaviour.


