6bcf5a9e17
This is a draft - merge 4700's into 4600s - remove old numbers in the square brackets - remove notation of when RFP kicked in (that info is in 4500s) - since we now do not recommend this section - cleanup info on each release in README section - do away with one char flip - move 4616 to deprecated where it belongs - remove "optional if..." lines - start cleaning up references, descriptions to shorten the section - will list what I removed: e.g. bugzillas to when the pref was added are a bit useless todo / consider - 4600 title - 4600 section description can be a lot better - 4600 link to wiki page on RFP ( issue #1218 - that is, if RFP is not for you, then just use Canvas Blocker, which can leak but should fool naive scripts if any get thru etc ) - do we want to add dom.enable_performance_navigation_timing while these all fit together as "covered by RFP", some of these seem out of place - maybe we could split this into two - 4600: "optional without RFP" - these won't hurt RFP but they also won't help your fingerprinting - e.g. font vis, prefers-color, prefers-reduced-motion - 4700: "do not use EVER especially with RFP" - these will affect RFP, can break shit, etc, and won't help your fingerprinting - e.g. all the timing stuff, disabling APIs, etc - also. the webgl one seems a bit out of place since we disable webgl - we could always move some items back to their relevant sections as inactive with some sort of RFP tag/warning I'm not sure what's the cleanest way to convey this. Anyway, pushing a PR to get some discussion going
🟪 user.js
A user.js is a configuration file that can control hundreds of Firefox settings. For a more technical breakdown and explanation, you can read more on the overview wiki page.
🟩 the arkenfox user.js
The arkenfox user.js is a template which aims to provide as much privacy and enhanced security as possible, and to reduce tracking and fingerprinting as much as possible - while minimizing any loss of functionality and breakage (but it will happen).
Everyone, experts included, should at least read the implementation wiki page, as it contains important information regarding a few user.js settings.
Note that we do not recommend connecting over Tor on Firefox. Use the Tor Browser if your threat model calls for it, or for accessing hidden services.
Also be aware that the arkenfox user.js is made specifically for desktop Firefox. Using it as-is in other Gecko-based browsers can be counterproductive, especially in the Tor Browser.
🟧 sitemap
🟥 acknowledgments
Literally thousands of sources, references and suggestions. Many thanks, and much appreciated.