[SOLVED] Some thoughts on Pale Moon vs Firefox

nycace36 · 02-14-2021, 08:24 PM

Quote:

Originally Posted by cwizardone

Pale Moon v29.0.1 has been released.
https://www.palemoon.org/releasenotes.shtml

khronosschoty's v29.0.1 SBo pkg64 for Slackware 14.2 available at http://repo.khronosschoty.org/Slackw...6_64-1_SBo.tgz
Official SlackBuild Repository for the same at http://slackbuilds.org/repository/14...work/palemoon/ with better description and all Source Download links

--

khronosschoty · 02-14-2021, 09:58 PM

Quote:

Originally Posted by nycace36

Yeah, and the Implementation notes part of that v29.0 Release Notes page specifically states..

So therefore is PM v29.0 simply enabling or actually increasing its Google tie-in through its implementation of that "good chunk of Google WebComponents", hmm??
As 'individual' previously noted in this very thread ~3mos ago (11-04-20), Slackware's alienbob hasn't exactly been any big fan of Pale Moon at all, see Pale Moon browser removed from my repository

OTOH, ISTR that Firefox doesn't have much appreciable Google tie-in if any tie-in at all(?)

Even more so, can that Google tie-in in Pale Moon v29.0 even be further removed to any desirable extent in khronosschoty's or others' upcoming SlackBuild releases(s) (not yet available at the time of this writing) at http://repo.khronosschoty.org/Slackware/Pale-Moon/ ??gazooks!!

Somewhat-germaine to this is my recent LQ forum post for the Chromium browser; alienbob's take on chromium for slackware

--

feel free to offer patches; otherwise I wouldn't mind taking a look and seeing about creating some patches myself -- when I have time that is.

cwizardone · 03-02-2021, 09:21 AM

Pale Moon v29.1.0 has been released.

Quote:

v29.1.0 (2021-03-02)
This is a development, bugfix and security update.

The change log, https://www.palemoon.org/releasenotes.shtml

cwizardone · 03-30-2021, 09:50 AM

Pale Moon v29.1.1 has been released.

Quote:

v29.1.1 (2021-03-30)
This is a minor security and bugfix update.
Changes/fixes:
Updated NSS to fix certificate import and keygen regressions.
Removed restrictions for units of width/height attributes on SVG elements.
Enabled scrollbar-width CSS keyword by default.
Security issues addressed: CVE-2021-23981 and a DiD fix for potential document parser confusion.
Unified XUL Platform Mozilla Security Patch Summary: 2 DiD, 9 not applicable.

https://www.palemoon.org/releasenotes.shtml

cwizardone · 03-31-2021, 10:21 PM

For the last several hours the Pale Moon web site has looked like this, regardless of which browser is used.
Is it something on their end or my end or is it a early April Fools' Day joke?

Gordie · 03-31-2021, 10:43 PM

Quote:

Originally Posted by cwizardone

For the last several hours the Pale Moon web site has looked like this, regardless of which browser is used.
Is it something on their end or my end or is it a early April Fools' Day joke?

Funny. The word DONATE is spelled in English but the rest is Swahili

PROBLEMCHYLD · 03-31-2021, 11:03 PM

From my tablet

kgha · 04-01-2021, 05:10 AM

At forum.palemoon.org I read:

Quote:

The forum is currently off-line for language maintenance.

cwizardone · 04-02-2021, 01:17 PM

Turns out it was their idea of a April Fools' Day joke.
https://forum.palemoon.org/viewtopic...=26503#p211883

Those people really need a serious attitude adjustment.

cwizardone · 04-27-2021, 10:08 AM

Pale Moon v29.2.0 has been released.

Quote:

v29.2.0 (2021-04-27)
This is a development and bugfix release.
Starting with this version, we will no longer be supporting unmaintained legacy Firefox extensions that are not updated for/targeting Pale Moon directly.
Please see this forum post for details. https://forum.palemoon.org/viewtopic.php?f=1&t=26657

Changes and fixes,
https://www.palemoon.org/releasenotes.shtml

kgha · 04-29-2021, 01:36 AM

Dropping legacy support means that a favourite plugin, epubreader, no longer works in palemoon. So thank Bob for seamonkey. Apart from that I have no issues with the new release.

cwizardone · 04-29-2021, 10:51 AM

Quote:

Originally Posted by kgha

Dropping legacy support means that a favourite plugin, epubreader, no longer works in palemoon. So thank Bob for seamonkey. Apart from that I have no issues with the new release.

The Click&Clean button no longer works after the "update" so I've reverted to the previous version of Pale Moon.

kgha · 06-09-2021, 03:31 AM

Palemoon-29.2.1 released (bugfix: http://www.palemoon.org/releasenotes.shtml )

ttk · 06-10-2021, 01:26 PM

I've been using Basilisk (by the same dev team as Pale Moon) for the last few days, to kick the tires and figure out if it's a viable migration path from Pale Moon. I'm not looking to leave Pale Moon just yet, but the dev team has made it clear that they will be deprecating Pale Moon eventually and focusing on Basilisk.

Basilisk does almost everything I require, and ticks more of the boxes on my "nice to have" list than other browsers I've tried (Firefox, Chrome, Brave). Its current shortcomings, for my purposes:

* I can't figure out how to give it Emacs keybindings. For Pale Moon it's just a matter of putting gtk-key-theme-name = "Emacs" into ~/.gtkrc-2.0, but Basilisk ignores ~/.gtkrc-3.0 (it is gtk-3 based). Maybe I'm just doing this wrong.

* It doesn't work correctly with GitHub, a problem it shares with Pale Moon.

* It bloats out and slows down very quickly. I had to restart it after four days, whereas I don't have to restart Pale Moon for usually forty to seventy days.

I could learn to adapt to all of these except for the last. I really don't like restarting my browser. If it gets to the point where it only has to be restarted every thirty days, I could tolerate that.

Since Basilisk is still a work-in-progress, and Pale Moon is still a viable solution, I'll stick with Pale Moon for a while longer and let Basilisk absorb more debug/deploy/test cycles before trying it again.

derekn13 · 06-11-2021, 01:15 AM

Quote:

Originally Posted by ttk

* I can't figure out how to give it Emacs keybindings. For Pale Moon it's just a matter of putting gtk-key-theme-name = "Emacs" into ~/.gtkrc-2.0, but Basilisk ignores ~/.gtkrc-3.0 (it is gtk-3 based). Maybe I'm just doing this wrong.

I haven't tried Basilisk (yet), but I've been using the gtk3 version of Palemoon. The config file is ~/.config/gtk-3.0/settings.ini, and the relevant content is:

Code:

[Settings]
gtk-key-theme-name = Emacs

Hopefully that works for Basilisk, too.