summaryrefslogtreecommitdiffstats
path: root/debian/local
diff options
context:
space:
mode:
Diffstat (limited to 'debian/local')
-rw-r--r--debian/local/pref/user.js29
1 files changed, 0 insertions, 29 deletions
diff --git a/debian/local/pref/user.js b/debian/local/pref/user.js
index 8d1adb3be4..f4deaae5dd 100644
--- a/debian/local/pref/user.js
+++ b/debian/local/pref/user.js
@@ -5,35 +5,6 @@
* url: https://github.com/arkenfox/user.js
* license: MIT: https://github.com/arkenfox/user.js/blob/master/LICENSE.txt
-* README:
-
- 1. Consider using Tor Browser if it meets your needs or fits your threat model
- * https://2019.www.torproject.org/about/torusers.html
- 2. Read the entire wiki
- * https://github.com/arkenfox/user.js/wiki
- 3. If you skipped step 2, return to step 2
- 4. Make changes in a user-overrides.js
- * There are often trade-offs and conflicts between security vs privacy vs anti-tracking
- and these need to be balanced against functionality & convenience & breakage
- * Some site breakage and unintended consequences will happen. Everyone's experience will differ
- e.g. some user data is erased on exit (section 2800), change this to suit your needs
- * While not 100% definitive, search for "[SETUP" tags
- 5. Some tag info
- [SETUP-SECURITY] it's one item, read it
- [SETUP-WEB] can cause some websites to break
- [SETUP-CHROME] changes how Firefox itself behaves (i.e. not directly website related)
- 6. Override Recipes: https://github.com/arkenfox/user.js/issues/1080
-
-* RELEASES: https://github.com/arkenfox/user.js/releases
-
- * It is best to use the arkenfox release that is optimized for and matches your Firefox version
- * EVERYONE: each release
- - run prefsCleaner to reset prefs made inactive, including deprecated (9999s)
- ESR102
- - If you are not using arkenfox v102-1... (not a definitive list)
- - 2815: clearOnShutdown cookies + offlineApps should be false
- - 9999: switch the appropriate deprecated section(s) back on
-
* INDEX:
0100: STARTUP