michel_ouba/FF_arkenfox_user.js
michel_ouba/FF_arkenfox_user.js
1
0
Fork 0
Code Releases Activity

still drafting...

Browse Source
This commit is contained in:
Roman-Nopantski 2017-02-20 15:45:58 +13:00 committed by GitHub
parent 6435c2795a
commit 894dda6d60
1 changed files with 14 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
README.md
View File

@ -10,36 +10,38 @@
- discuss why use a js (enforcement on startup, migration)
- outline trade-offs between security vs privacy etc
- explain expectations and site breakage
- explain this version is "middle to high road" with very little breakage (but it will happen) but is only a starting point
- explain this version is a "compromise" or balance that aims (with addons eg you WILL need uBlock Origin or turn safe browsing and tracking protection back on) to provide as much privacy and enhanced security as possible, and to reduce the fingerpritning attack surface as much as possible - while putting up with some incoveniences and as little site breakage as possible (but it will happen). It's only a starting point.
- provide troubleshooting: site breakage will happen. 90=% of the preferences cause no issues. It is only a small core of settings that people may or may not need to look at, depending on their objective.
- no one size fits all, this is a template, fork it! Customize it! (see goals, we won't set you wrong)
### Goals & Standards
To be **THE** template and resource all other user.js' come to for news, links, information and more, which means it needs to be:
- comprehensive (mention prefs are included at default for completeness/enforcement, alot are included and changed for future-proofing, etc)
- comprehensive (eg some prefs are included at default for completeness/enforcement, a lot are included and changed for future-proofing, etc)
- current and available and change-trackable (hey, we're on github now)
- easy to understand (good simple less-techincal descriptions)
- accountable and a resource (lots of links to authorative authors and tech papers etc)
- easy to understand (good, simple, less-technincal descriptions)
- accountable and a resource (lots of links to authorative authors and tech papers, also repo wiki)
- correct and to dispell myths and bad advise (see accountable)
- eassy to follow and report and discuss (logical numbered structuring)
- eassy to follow and report and discuss (logical and numbered structure)
- give good advise (see trade-offs)
- expanded on with more information, such as FF version numbering for introduction and deprecation of preferences
- expanded on with more information, such as FF version numbering for introduction and deprecation of preferences, hidden pref tags etc
- archived for each stable release (starting with 51)
- to provide illustrated wiki topics to help
- to make it as easy as possible for anyone to use a user.js and get it right
- to provide two or three future forks with differnent settings from painless no-breakage, thru to super-hardened for use with multiple profiles
- to provide illustrated wiki topics to help (help wanted please!)
- to make it as easy as possible for anyone to use a user.js and get it right for them
- to provide two or three future forks with differnent settings from "painless no-breakage no-addons" thru to a "super-hardened" version: for use with multiple profiles
### Implementation
- expectations of the user
- link to wiki on testing and tweaking in a portable FF first
- backup first: link to wiki articles on backup & restore methods
- backup first: link to wiki article on backup & restore methods
- changing, resetting preferences: user.js and about:config
### Troubleshooting
- wiki links
### Help & Resources
- Wiki links, appendices etc
- wiki links, appendices etc
### Acknowledgements
- yada yada