61ed383e71
This pref (in FF118 or lower) was applied regardless of 'intl.accept_languages', but only makes sense when it is "en-US, en" (which we used to set) But we removed 'intl.accept_language' in this release because there is no longer any RFP formatting protection, so we should no longer decide what language users prefer. Removed so users are not constantly reset on prefsCleaner, which could differ from what the user has/wants and be super annoying If 'use_us_english' were left active for ESR users who insist on using the live version, this would therefore have their language formatting set to en-US regardless of what they request - which would be annoying/confusing if they weren't requesting english and herein ends my story - make it inactive
🟪 user.js
A user.js is a configuration file that can control Firefox settings - for a more technical breakdown and explanation, you can read more in the wiki
🟩 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 wiki, as it contains important information regarding a few user.js settings. There is also an interactive current release, thanks to icpantsparti2.
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.