It's not deprecated.
Either it's an RFP alternative now that RFP indirectly covers it: i.e RFP prompts you on non en-US builds to spoof your language, and if you choose to spoof as en-US, then this solves that. If you're not spoofing your locale, then the pref has no significance.
Or we can remove it entirely: as I see no point in it TBH. If you're on en-US, then you're not leaking. If you use RFP + opt in to language spoofing, you're covered now. If you use RFP and opt out of language spoofing, then you're not leaking anything because you're telling the truth as per other language/locale metrics: i.e you don't need to spoof.
95% of me says we just remove the pref. 5% of me says - see what Earthlng thinks
I don't think we need a 4 yr old article to explain the concept of `.min` (or `.max`), it's pretty self explanatory (and SSL 3 is obsolete). Three lines of text culled, and one of the remaining http links eliminated as a bonus. Enjoy the saved bytes and mouse-scrolling.
De-duplicates many lines because the -ESR and -RFPalts options require too much boilerplate garbage. The script was unreadable enough without repeating code.
I don't think these changes deserve opening yet another PR, but please let me know if you disagree.
- no need to enforce defaults (except the second cross-origin) = less items in prefs and about:support
- simplify header info
- add in that you need an extension for real control: i.e for most people, e.g I use uMatrix and have never can to whitelist anything. Kolanich has been on settings of 2 for years and only found one broken site: these are anecdotal and don;t reflect the real world: which is why the settings are pretty relaxed
- move the broken info out of header and onto the pref in a setup tag
- reference: https://github.com/ghacksuserjs/ghacks-user.js/issues/716#issuecomment-488527274
- thanks Kolanich and 🐈
