I use Pale Moon 24 most of the time. I currently
have FF 36 installed, which I use with NoScript in
cases where I need to enable script/cookies/frames.
(I installed K-Meleon 75 and set it up, but haven't got
around to trying it.)
Every once in awhile, when I'm feeling like I have the
stomach, I try another version of FF and see what it
breaks. :) But I currently see no reason to venture into
the 40s. I'm already running a half dozen extensions and
numerous prefs settings to fix what's broken in 36,
and I still can't entirely eliminate tabs, which I very
much dislike. I just don't have the time and ambition
to keep track of what needs fixing in successive versions
of FF.
I don't even remember why I installed 36. But I
do remember that I had to install Classic Theme Restorer
just to get rid of the inane Bookmarks toolbar, which now
seems to be a forced element.... Bookmarks toolbar
forced but program menu is hidden and has to be
restored. It gets more bizarre with every version. I'll
say one thing for the Mozilla UI designers, though:
At least they don't totally disrespect UI preferences
the way that Chrome does.
In any case, I've confirmed that Secret Agent
works in FF 36. It has an ETags spoofer, among other
things, and is very unobtrusive in use. I don't use
the dynamic userAgent spoofer, though. I generally
travel with a generic UA in PM that says I'm on Win7
with a recent version of FF. If you rotate UAs
dynamically you end up with two problems:
1) Sites checking UA to optimize pages may break if
you pretend to be using a different browser. (IE and
everything else *really* don't mix.)
2) You become far more recognizable as unique because
you're the only visitor who appears to be loading ever file
with some different, funky, obscure browser. :)
| I am testing uMatrix (same author as uBlock Origin that I also use)
| which includes blocking 3rd party images and 3rd party referer.
user_pref("permissions.default.image", 3);
Note that this setting was deliberately broken at
some point by removing it from the settings and
changing the name of the setting. Some online
sources will show the old, outdated setting name
and value options.
Very handy setting. I use it in PM as default, but it will
often block captcha images and also blocks many
images on sites. For instance, if
bbc.co.uk loads
images from, say,
bbc-img.co.uk then you won't
see them. A surprising number of sites are poorly
designed in that way. And there's no way to fix
it. One would need whois analysis to connect
bbc-img with bbc.
user_pref("network.http.sendRefererHeader", 0);
user_pref("network.sendRefererHeader", false);
They've broken that one at least once and I forget
which is the current value, so I just have both set.
And this, for good measure:
network.http.sendSecureXSiteReferrer false
With script enabled you're a sitting duck, both
security-wise and privacy-wise. And it's hard
to know about all the things that apply. (Until
the recent geo-location thread I didn't know that
worked in other browsers.) But I guess you have
one advantage for privacy: Enabling script makes
your profile online less unique and therefore more
anonymous. Though I wonder how much that really
applies. A site can see that I'm an unusual visitor,
if they care to, just by checking whether script
is enabled. But they don't have much of a way to
label that uniqueness.
Disabling script is increasingly becoming an art
form. At MS support pages I have to put the URL
into Google now and read the cache version. Some
sites try to thwart no script by putting a giant,
blank overlay on their page, so that I need to
read it with no style. Many sites are partially
broken through simple ignorance. Even the page with
the etiquette for this group is faulty. I have to read
it with no style to see all the text.
https://www.mozilla.org/en-US/about/forums/etiquette/
And some sites will use the trick of sending the
browser into a loop if script is disabled, so I have
this setting meant for accessibility:
accessibility.blockautorefresh true
It's getting nasty out there. :)