michel_ouba/FF_arkenfox_user.js
michel_ouba/FF_arkenfox_user.js
1
0
Fork 0
Code Releases Activity
Fork de https://github.com/arkenfox/user.js
1,622 Commits 1 Branch 0 Tags 3.6 MiB
JavaScript 71.5%
Shell 16.3%
Batchfile 12.2%
ca99add006
Go to file
Thorin-Oakenpants ca99add006
turn ETP on everywhere 
It literally cannot hurt [1], and makes it easier for users to use custom mode with TCP/dFPI. Turning on socialtracking helps gain parity with strict mode

[1] gorhill: https://old.reddit.com/r/firefox/comments/l7xetb/network_priority_for_firefoxs_enhanced_tracking/gl9rn9n/
> All extensions and ETP work in parallel, they all inspect network requests and all make the decision to block or not, hence if they all decide to block, they will all report that they block something. ETP is a bit different than normal extension in that it will give precedence to an extension trying to redirect to a local resource, this ensures ETP works harmoniously with normal extensions.
> 
> Once something is not blocked, it then goes through a DNS query, and the browser waits for the response.
> 
> I will add examples of how ETP + multiple blocker extensions work together when dealing with a network request; let's say "A" and "B" are two different blockers:
> 
>   - ETP=block, A=allow, B=allow: result=block
>   - ETP=allow, A=block, B=allow: result=block
>   - ETP=allow, A=allow, B=redirect: result=redirect
>   - ETP=allow, A=block, B=redirect: result=block
>   - ETP=block, A=allow, B=redirect: result=redirect
> 
> So as you can see, ETP is a bit different than a normal extension in that it won't prevent redirection from happening if ever a network request is redirected by one of the normal extension.
2021-04-04 11:49:07 +00:00
.github/ISSUE_TEMPLATE add override recipes 2020-12-25 15:55:01 +00:00
scratchpad-scripts browser.send_pings.require_same_host 2021-04-03 14:25:46 +00:00
wikipiki Add files via upload 2021-03-11 14:06:38 +00:00
_config.yml migration: cleanup code references 2020-09-15 06:07:32 +00:00
.gitattributes Update .gitattributes 2019-06-26 13:32:12 +00:00
.travis.yml Added Travis CI configuration 2017-03-01 00:11:05 +02:00
LICENSE.txt Update LICENSE.txt 2020-09-15 04:19:03 +00:00
prefsCleaner.bat v2.4 - add strlen check for prefs.js 2021-01-17 15:27:50 +00:00
prefsCleaner.sh Update prefsCleaner.sh 2020-09-15 11:55:28 +00:00
README.md clean up acknowledgments 2020-10-20 12:57:00 +00:00
updater.bat v4.14 - check for TLS1.2 (#1097) 2021-01-22 12:15:12 +00:00
updater.sh v3.0 - improve readIniFile() (#1128) 2021-03-07 13:29:33 +00:00
user.js turn ETP on everywhere 2021-04-04 11:49:07 +00:00

README.md

🟪 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

License: MIT

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.