28 karma · joined November 16, 2022
There is already a similar issue with forks for Windows XP called New Moon and My Pal - Pale Moon long since dropped support for XP yet users of these builds show up on the forum asking for help instead of asking the fork maintainers.
Mozilla went hardcore political and Chrome copycat long after his time. There was no such controversy there under Eich, and even now as Brave's CEO he isn't doing anything to 'influence public opinion'. Browser CEOs aren't newspaper editors or activists, Mitchell Baker excepted.
And he's complaining about NoScript, which doesn't play well with Pale Moon to the extent of destabilizing the browser and whose Pale Moon compatible XUL version is long abandoned by its developer while there's an alternative (eMatrix, forked from now abandoned uMatrix that was made by uBlock Origin's author) available. (https://forum.palemoon.org/viewtopic.php?f=46&t=17619)
Pale Moon is what Firefox used to be once upon a time in terms of customization and privacy before Mozilla became Google's controlled opposition to guard against browser monopoly allegations.
The only thing 'outdated' is their not jumping on the minimalist, mobile focused UI that Chrome invented and Firefox copied and retaining a sane, desktop user focused and fully customizable UI that doesn't need digging into about:config or userChrome.css tweaks and can be directly done from the preferences dialog or context menus. The way Firefox used to be until version 4 onwards when the copying Chrome and limiting user choice began. To your last point, why should you have to tweak Firefox for privacy at all when they keep proclaiming how privacy friendly they supposedly are? Pale Moon is private out of the box - there is no baked in telemetry (they don't run a telemetry server, for starters), analytics, tracking, advertising or anything else on those lines.
Mozilla had a separate XULRunner runtime to bundle with your app for it to be fully standalone, or you could invoke it with the locally installed Firefox instance. There were several, like Songbird (media player), FireFTP/FireSSH (originally began as extensions and now available as standalone software)
It's exactly the same attitude of 'this site requires IE6' from the early 00s, but with worse results.
Mostly not even bothering to inform you that you didn't make it to the interview round.
And ironically for all the talk of making it more secure, the amount of cross browser malware has only shot up since Mozilla decided to dump XUL in favor of copying Chrome's extension system.
>While FF is still the best browser for me (barely)
Give Pale Moon a try and ignore the FF fanboy propaganda of it being oLd aNd iNSeCuRe. It isn't, it's regularly updated to keep up with Google dominated web standards and security patches, and runs on an independent fork of Firefox's Gecko rendering engine. It is not a mere rebuild like Librewolf, Waterfox etc but a separate browser that retains all the full customizabiity of pre 2017 Firefox with full XUL extension and NPAPI plugin support.
about:config already has a warning when you first open it that you'll screw up your settings if you don't know what you're doing. So if someone borks their install as a result, it isn't Mozilla engineer's job to apologize or hand hold them through it.
Every software until the 2010s (Windows itself, with its registry) has had this implicit disclaimer that you forfeit all official support if you dick around with the internals in an non standard way. So why is it now at the other extreme of 'fuck all power users, we will only target those who can't walk and chew gum simultaneously' ?
And goes without saying, full support for powerful XUL extensions and full themes that actually extend the browser's functionality and change its appearance the way it used to be on Firefox back in the day.
In stark contrast to the previous norm of highly customizable software that catered to both newbies and power users. Right here we see the example of the maintainer unilaterally deciding to strip out a feature that's already been disabled, just because he decided he knows better what KeepassXC users ought to do.