9018577a3e
- add -s parameter to start immediately / skip prompt / run non-interactive This is useful if the user wants to automate the process of updating the user.js and cleaning prefs. - fQuit: error messages to stderr - fFF_check: info msg to stderr Better support for suppressing/redirecting stdout while still showing any error messages in the console, useful for example with `prefsCleaner.sh -s >/dev/null` |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| scratchpad-scripts | ||
| wikipiki | ||
| _config.yml | ||
| .gitattributes | ||
| .travis.yml | ||
| LICENSE.txt | ||
| prefsCleaner.bat | ||
| prefsCleaner.sh | ||
| README.md | ||
| updater.bat | ||
| updater.sh | ||
| user.js | ||
🟪 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.