Today I recently rediscovered #PaleMoon, a web browser forked long ago that resembles an ancient version of #Firefox.

What are your #thoughts on it? Just curious to see what people here think! 😄

#UnoLinux
Ciao a tutti, stavo pensando di provare ad usare #Palemoon browser per un po'... Ma la cosa che mi blocca e non trovarlo nei repo di #debian o come #flatpak ...

Che ne dite è un progetto affidabile? Che cosa se ne dice in giro?

@martinschlegel @Extelec Pretty much any version of #NetBSD should run on a #ThinkPad T23 out of the box, and #pkgsrc will include the ~latest #firefox. I tested it on a ThinkPad T41, which is only two years more recent than the T23 - https://youtu.be/jYS4TcgxMxU

Now, whether you can do anything *useful* in modern Firefox on a 1GB 32 bit machine... not so much

#PaleMoon or #ArcticFox are pretty capable browsers which run well on smaller machines - and #Dillo will *scream* on that spec hardware 😛

Well, there's no need to on #palemoon :^)

https://io.mwl.io/@mwl/114268495049973834

Cloudflare is now asking browser devs to sign #NDAs that are longer than the Iliad just to fix some petty browser blockages. 🤯 Meanwhile, the Pale Moon #forum users are busy discussing the existential relevance of General #Discussion. 🤔💫
https://forum.palemoon.org/viewtopic.php?t=32127 #Cloudflare #BrowserDev #PaleMoon #TechNews #HackerNews #ngated

Let’s just say there’s a reason #PaleMoon has never adopted the idea of signing add-ons…

https://support.mozilla.org/en-US/questions/1468274

Also equating “cool customisation” to “security risk” as well as downplaying the transition from #XUL to #WebExtensions as one of making add-ons “more secure” (which is questionable because there are a lot more malware in the #Firefox add-ons site now than back in the XUL era) instead of making them less powerful is really Orwellian and shows how #Mozilla has cared less and less about what made their browser obviously unique and different from the competition (which struggled in making their browsers customizable and extensible). A betrayal of the power users who believed in the power and future of what they’ve built; the same users who helped spread Firefox to the point it looked like it was unstoppable in being the browser who will crush MSIE once and for all! Until Chrome came and Mozilla tried imitating it…

#ThereIsOnlyXUL #openweb #browsers

A look at #Firefox forks

https://lwn.net/Articles/1012453/

#Mozilla #GNU #IceCat #Floorp #LibreWolf #Zen #Basilisk #Waterfox #PaleMoon #SeaMonkey #OpenSource #FLOSS #FOSS #browser #browsers

#PaleMoon is so compliant with web standards that it becomes a #webcompat issue lol: https://forum.palemoon.org/viewtopic.php?f=70&t=32165

Where the browser should have given a SyntaxError for:

document.querySelectorAll('a[target="_blank"]:not([class*="modal-video"]')

..the mainstream (i.e. #Chrome / #Edge, #Firefox, and probably #Safari too) just doesn’t and instead ignores the missing closing parenthesis for querySelectorAll like the error isn’t there at all…

What’s even more frustrating is that #Mozilla knew about this bug for 12 years and decided not to fix it because of their wrong interpretation of the spec: https://bugzilla.mozilla.org/show_bug.cgi?id=815662

#openweb #JavaScript #CSS #querySelectorAll

I’ve been waiting for @european_alternatives ‘s chat to become available for quite a while, but I guess they’re just always “away for the moment”… Oh well, I’ve sent them the suggestion anyway to include #PaleMoon to their list of European web browsers (since it’s based in Sweden and the main developer is Dutch), hopefully they’ve received it :meowcoffee:

#openweb #browsers #EuropeanAlternatives

How does #PaleMoon compare to other web #browsers when it comes to the security of synced data?

Pale Moon ( #Weave ):

• Your secret key is never sent to our servers, we only have encrypted data which we can never read without your key :KanneThumbsUp:
• Pairing a new device while having an already synced device nearby is easy and does not need your sync account’s email and password, while still being cryptographically secure: the target device can generate a random 12-character code which will be inputted in the device already synced with your account in order to complete pairing. This preferred “quick link” method uses J-PAKE to transfer credentials and the secret key without having to show them to the screen, therefore avoiding key disclosure better. See our docs: https://www.palemoon.org/sync/help/easy-setup.shtml
• If an already synced device is not nearby, then you will need your account’s email and password. To get the synced data, you will need a copy of your secret key. If you don’t have access to any synced device which will have your key, then you can generate a new one within the browser itself (after logging in with your credentials), but all synced data stored in the server will be inaccessible and erased. :KanneThumbsUp:
• The sync service is not meant for long-term backup and our storage is limited, therefore we limit each account’s sync storage to 30 MB, and if your account has not been synced for 2 or 3 months straight, we schedule your synced data or account respectively for deletion in the next maintenance window.
• Resetting your sync account’s password within the browser is not yet supported. However as long as nobody has your key, nobody will ever be able to access it, and given enough time, your data in encrypted form will not even be in our servers anymore because of the regular maintenance. For now you will have to DM Moonchild on the forums to get him to delete your account so you can re-register: https://forum.palemoon.org/viewtopic.php?f=52&t=31143&p=251609#p251616
• Sync service can be self-hosted! Source code for the implementation we use can be found at https://repo.palemoon.org/Moonchild/FSyncMS. It is basically a minimal #Weave / Sync 1.1, which is the previous sync system Mozilla used before Firefox 29 moved to Sync 1.5 + FxA, and it requires a LEMP stack.

Mozilla Firefox ( #FirefoxSync ):

• Synced data cannot be read by Mozilla :KanneThumbsUp:
• Your secret key is sent to Mozilla’s servers, but it is first hashed client-side with your Firefox Account’s (FxA) password before it’s sent :02think:
• This means by default (i.e. one didn’t place a 2FA in their FxA) one can pair a new device and recover their synced data as long as one knows the FxA password, even if they can’t access any of the synced devices. The security of your synced data depends solely on your FxA password (which is why we didn’t adopt it and kept/brought back Sync 1.1 even if it got completely removed by the time we made our final hard fork of Firefox 52 ESR’s platform code) :02think:
• If you forget your Firefox account’s password and reset it, your previously synced data will be inaccessible :KanneThumbsUp:
• Can be self-hosted, but truly self-hosting everything is a bit complicated because the sync service is dependent on FxA’s authentication service which is its own server. :02think: Docs can be found here: https://mozilla-services.readthedocs.io/en/latest/index.html

Google Chrome:

• Synced data can be read by Google by default :cat_stare:
• Data can be made unreadable even to Google by setting a passphrase, but that’s dependent on the passphrase’s strength :02think:
• Resetting your passphrase will make previously synced data inaccessible :KanneThumbsUp:
• Authentication can be three-factor: your Google account’s password, then the Google account’s own 2FA (e.g. TOTP), and lastly the local passphrase.
• Details about the sync system is obscure, so the above is based on what we probably know. :shrugakko: Obviously this means Chrome’s sync can’t be self-hosted

#sync #mozilla #firefox #google #chrome

I replaced #Firefox with #Palemoon and it works perfectly.

#LittleThings