Long-term solution for CF and other site issues?

Talk about code development, features, specific bugs, enhancements, patches, and similar things.
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.

This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.

Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
User avatar
noellarkin
Fanatic
Fanatic
Posts: 120
Joined: 2021-07-27, 04:20

Long-term solution for CF and other site issues?

Post by noellarkin » 2024-06-07, 04:34

I started thinking about this after the Cloudflare issues earlier this year: How difficult would it be to set PaleMoon up so it always mimics the latest version of Firefox in the UserAgent passed in HTTP requests, as well as WebWorkers (as of now, it seems that even if the UA is spoofed, the real UA is leaked by WebWorkers)?
It seems to me that CF is going to keep prioritizing the most common browsers, Chrome and Firefox - - and the same goes for many websites.
Since PM's engine is more similar to FF than it is to Chrome, would it be extremely difficult or impossible for Pale Moon to emulate FF's fingerprint out-of-the-box?
Wouldn't that be a good long-term solution?
Something similar to what Tor project does: just mimic a commonly used version of FF.

User avatar
moonbat
Knows the dark side
Knows the dark side
Posts: 5747
Joined: 2015-12-09, 15:45

Re: Long-term solution for CF and other site issues?

Post by moonbat » 2024-06-07, 05:49

This is the wrong approach because PM would be advertising itself as what it isn't - and other sites would break if they attempted to use FF specific features. It's not something that can be fixed at the browser side of things IMO, we will have to grin and bear it with Cloudflare.
"One hosts to look them up, one DNS to find them and in the darkness BIND them."

Image
KDE Neon on a Slimbook Excalibur (Ryzen 7 8845HS, 64 GB RAM)
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX
Jabber: moonbat@hot-chili.net

User avatar
Moonchild
Project founder
Project founder
Posts: 38728
Joined: 2011-08-28, 17:27
Location: Sweden

Re: Long-term solution for CF and other site issues?

Post by Moonchild » 2024-06-07, 10:02

TOR can get away with it because it's a rebuild of Firefox, not a fork. They are effectively the Firefox version they say they are in their UA.
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
noellarkin
Fanatic
Fanatic
Posts: 120
Joined: 2021-07-27, 04:20

Re: Long-term solution for CF and other site issues?

Post by noellarkin » 2024-06-07, 14:49

moonbat wrote:
2024-06-07, 05:49
and other sites would break if they attempted to use FF specific features
True, but it seems many sites are breaking not because of feature issues (PM can open most sites these days) but because of stupid browser UA whitelists/blacklists. Wouldn't hard-coding a Firefox UA into PaleMoon get rid of that problem, atleast? The more usable PM is, out-of-the-box, the more user adoption.

User avatar
Moonchild
Project founder
Project founder
Posts: 38728
Joined: 2011-08-28, 17:27
Location: Sweden

Re: Long-term solution for CF and other site issues?

Post by Moonchild » 2024-06-07, 16:44

Firefox compatibility mode is the default for a reason. We already present a "somewhat compatible" Firefox UA to websites. For websites that need specific other strings than our defaults, we have site-specific user-agent overrides (for which some extensions have been made to make it easier to enter them, e.g. Sasuga).
We're already doing everything we reasonably can. As long as websites keep discriminating, we'll have to deal with these symptoms. it's just the way it is. We can't force them to be more broadly compatible; that is up to them.
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
back2themoon
Knows the dark side
Knows the dark side
Posts: 3090
Joined: 2012-08-19, 20:32

Re: Long-term solution for CF and other site issues?

Post by back2themoon » 2024-06-08, 10:01

Same old issue, unfortunately. As mentioned, mimicking moving, non-Goanna targets is not realistic. The best solution would be pushing for establishing Pale Moon / Goanna as an additional player/test platform.

And yes, all this has been discussed before: time and money required...