On 2018-04-01 09:15, Martin Vaeth wrote:
> If you speak about defenses like noscript, there are safer variants
> available. I guess the usage of the already mentioned user.js (of
> course adapted to your needs) together with current Webextensions
> noscript, ublock-origin, and https-everywhere (maybe for privacy also
> coupled with decentraleyes, duckduckgo{-privacy-esesntials},
> canvasblocker, skip-redirect) does protect you more than using old
> versions of these packages.
I'll look at these things. Didn't know ublock was available as a webext.
> Not to speak about freshly found security holes.
I have been looking at them since I adopted palemoon mid-yesteryear. It
seems to me almost all are in new code added to FF after the fork, and
moreover in code handling new web "features" which I never use.
> > This is a tangent from the thread topic, but there is another
> > inconvenience of modern FF that keeps me from re-adopting it: font
> > rendering.
>
> I do not have experience with this, but there is also a lot
> customizable in user.js (i.e. about:config). I guess you have
> to switch off (or on) some hardware acceleration. There is also
> a rich "themes" API which might contain relevant options.
Of course I'm no expert either (if I were, I would invest the effort to
make it work for me), but IMO this is not in FF proper but in the
bundled version of freetype - which cannot be unbundled via USE. So
it's all about this:
https://www.freetype.org/freetype2/docs/subpixel-hinting.html
and the reasons I can make it work with palemoon:
1. palemoon doesn't bundle freetype
2. I froze my freetype at 2.7.1, the last version where it can still be
disabled
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.
