FF_arkenfox_user.js

Go to file

earthlng 9ab13cec87 more typos beware of the big bad grammar nazi 😱		2017-02-19 17:20:20 +01:00
LICENSE.txt	Create LICENSE.txt	2017-02-18 08:57:08 +13:00
README.md	draft readme outline	2017-02-20 03:39:05 +13:00
user.js	more typos	2017-02-19 17:20:20 +01:00

ghacks-user.js

This is a rough draft, please read the old intro currently at the start of the user.js in the meantime.
Paragraph here about not jumping in without reading first, and backing up, and understanding the changes

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
no one size fits all, this is a template, fork it! Customize it! (see goals, we won't set you wrong)

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)
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)
correct and to dispell myths and bad advise (see accountable)
eassy to follow and report and discuss (logical numbered structuring)
give good advise (see trade-offs)
expanded on with more information, such as FF version numbering for introduction and deprecation of preferences
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