Firefox Configuration Guide for Privacy Freaks and Performance Buffs
1–10 of 125 posts
Re: Firefox Configuration Guide for Privacy Freaks and Performance Buffs
#2* No WebGL or WebRTC
* Aggressive TLS settings (will break many websites)
* Mixed-content upgrading (Nightly ran an experiment on this recently and it also broke a lot of websites)
* No history
The text warns about this, but it should at least be clear why Mozilla doesn't ship this as default.
Re: Firefox Configuration Guide for Privacy Freaks and Performance Buffs
#3Re: Firefox Configuration Guide for Privacy Freaks and Performance Buffs
#4This isn't the most unreasonable list I've seen, but beware you will break many websites with this, so you need to be prepared to deal with the fallout. Notably, a lot of the breakage is hidden in user.js, including: * No WebGL or WebRTC * Aggressive TLS settings (will break many websites) * Mixed-content upgrading (Nightly ran an experiment on this recently and it also broke a lot of websites) * No history The text…
- uBlock Origin in default configuration
- No 3rd party cookies (breaks some things, but not too many)
- Clear history and cookies on exit
Combined with an /etc/hosts file, and rather frequent browser restarts (generally daily).
Re: Firefox Configuration Guide for Privacy Freaks and Performance Buffs
#5For example, there is the feature of automatically loading resources, such as images. No user input required. There is the feature of automatically loading the contents of iframes. No user input required. There is the feature of cookie headers sent automatically. No user input required. There is the feature of XMLHttpRequest triggered through Javascript. No user input required. There is support for HTTP/2. Imagine websites pushing media to users computers with greater efficiency than ever before (advertisers rejoice). No user input required.
If one is serious about regaining control over the sending of user data to these corporations and websites ("privacy"), then IMO one needs a browser that either lacks or can disable the features above and any others that allow media to be "pushed" to the user without any user input. Such a browser would only execute GET or POST upon user input, not upon input from other sources, such as websites.
Perhaps users could have two browsers: one for commercial activity and running "web apps" and another for non-commercial activity, which may not need to be default compatible with "web apps" that push media to the user. This is an alternative to having to become an expert in browser settings.
Instead of disabling features or installing add-ons, the later browser is incapable of pushing unsolicited media or leaking user data because it lacks the necessary features to do so. (I have been using such a browser for many years now. While this is probably not for everybody, I like it.)
Re: Firefox Configuration Guide for Privacy Freaks and Performance Buffs
#6It doesn't stop sites pulling all cookies, but it reduces the amount of information being sent: only the information in the same container is accessible.
[1] https://addons.mozilla.org/en-US/firefox/addon/multi-account...
Re: Firefox Configuration Guide for Privacy Freaks and Performance Buffs
#7I'll note that disabling custom fonts breaks certain sites. I don't consider it a deal-breaker, but it's worth being aware. Many sites abuse fonts for icons. Developers, please consider using SVG icons instead.
Another comment mentioned how user.js disables WebGL and WebRTC. IMO, that and many other browser features should be disabled by default. If a site requires their functionality, I should be able to whitelist it. Safari used to let you conditionally enable WebGL access for only certain sites, showing a prompt when the functionality was accessed. It's a damn shame they removed the feature. I don't think most sites should have full access to all these browser APIs. Heck, all the storage APIs should probably be limited to the current session by default, with the option of requesting longer-term persistence for trusted services.
I'd really love it if we had an easy way to create fully isolated containers for each web service or group of web services, with varying tweaks in their security preferences.
Since we're already on the topic of configuring Firefox, I have a tangential question. Does anyone know how to configure Firefox to automatically save rar files? You usually receive the option to always save different file types, but the choice isn't available for rar files, so you always receive a download popup. It's quite annoying, and I have no idea why it happening. A cursory search didn't reveal any useful information on the matter. It's perplexing, because tar and zip files can be set to automatically save without any problem.
I hadn't seen uMatrix before, but it looks promising. Does anyone know of any user-friendly OS tools that lets you monitor and inspect requests? On macOS I used Little Snitch for a long time, but I'm trying to shift away from closed-source tools (no problem with paying, but I want to be able to compile it myself), especially for something so critical. Also, it doesn't let you inspect requests.
Re: Firefox Configuration Guide for Privacy Freaks and Performance Buffs
#8An opinion: The most serious threats to user privacy from advertising companies are the "features" of the browser that allow data to be sent to or from the users computer without any input from the user . In other words, the features that let developers of websites trigger GET and POST, to "push" media to the users computer and allowing "pulling" user data indiscrinately, without explicit consent and sometimes withou…
Re: Firefox Configuration Guide for Privacy Freaks and Performance Buffs
#9Re: Firefox Configuration Guide for Privacy Freaks and Performance Buffs
#10Privacy used to be a hobby for people with tinfoil hats or the monicker 'cypherpunk', but soon even Grandma will be going through a key signing ritual while muttering something about a return to the gold standard.
The least thing they could do is ask for it...
Edit: I shouldn't write early in the morning, tons of grammar mistakes.