1
0
mirror of https://github.com/arkenfox/user.js.git synced 2025-07-15 01:41:59 +02:00
Commit Graph

1187 Commits

Author SHA1 Message Date
4dd40bddcc 2 x gmp openh264 2019-04-29 18:22:39 +00:00
9da3cf4be8 1840: openh264: remove, see
Instead of being inactive, remove this. WebRTC is already blocked. And it can also be controlled by 1820. Redundant and does nothing extra for privacy, security etc
2019-04-29 18:21:01 +00:00
50869a734f [setup-*] always goes after [notes] 2019-04-29 18:13:47 +00:00
bb788682c9 fixup: remove duplicate pref 2019-04-29 17:44:53 +00:00
50afeb1861 0205: -> inactive, closes 2019-04-29 17:14:23 +00:00
0eb107abf3 3 x plugin prefs, see 2019-04-29 11:14:50 +00:00
675577fb8d 1800: remove redundant flash prefs, closes 2019-04-29 11:12:05 +00:00
b28677a594 1825: widevine update to inactive, see
- at worse, the update pref causes a security risk. I'll leave it in for now
2019-04-29 06:32:47 +00:00
48f3dfec84 browser.safebrowsing.downloads.remote.url 2019-04-29 05:31:17 +00:00
59930d4697 0402, remove redundant pref, see 2019-04-29 05:29:53 +00:00
579aa3aa9c 0402: tidy up, see 2019-04-29 05:27:16 +00:00
ed687fc7ca 1820: update -> inactive, see
At best disabling the background update of gmp means not only an extra item for those who wish to use it (e.g widevine, netflix) to have to deal with, but also a time delay in getting the actual download. At worst, it could cause users to use an old dll (security risk).

I will leave it in, for now, but am seriously considering removing it, so don't cry if I do.
2019-04-29 05:06:43 +00:00
ce3d5a8cbe 24 inactive SB+TP prefs, see 2019-04-29 04:52:58 +00:00
8ffbd81813 remove SB & TP see
- SB: disabling it nothing to enhance privacy/security etc if changed from default
- SB: I will not provide the prefs or encourage users to disable these, especially given that there is a UI
- SB: the urls are redundant
- SB: note: the binary checks stays
- TP section is out of date (or soon will be), I'm not maintaining it, it has a UI and is best handled there
2019-04-29 04:30:59 +00:00
4119be3a86 typo 2019-04-28 13:10:04 +00:00
8d874401fa pre FF61 deprecated -> archive
This is all archived in the sticky at the end of the first post
2019-04-28 12:56:27 +00:00
b4a4856223 3 x GMP prefs, see 2019-04-28 11:12:11 +00:00
8a86097997 1820s: GMP: remove three prefs, see 2019-04-28 11:10:15 +00:00
7a9763d129 2740: add setup tag etc, closes 2019-04-28 04:30:38 +00:00
a39516ff0e case consistency when using service worker* 2019-04-28 04:02:19 +00:00
3e5e1bfdd2 2740 -> inactive, see 2019-04-28 03:48:55 +00:00
7b667db766 2304 + 2305 -> inactive, see 2019-04-28 03:37:07 +00:00
8f1a489e36 3 update prefs, see 2019-04-28 02:58:35 +00:00
6f8d0263df 0303 + 0304 + 0305: remove, closes 2019-04-28 02:55:45 +00:00
25b8b404fb 2305+2306: musical chairs 2019-04-27 19:02:14 +00:00
528d0de6b4 2305: permission also applies to push 2019-04-27 17:39:53 +00:00
c9c1671e4a 2010+2012: simplify WebGL, closes 2019-04-27 16:18:48 +00:00
8765231de0 0801: keyword.enabled, closes
- explain pitfalls, add keyword tip, add setup tag
- given the searchbar is hidden by default in new FF installs, a lot of people could find this incredibly annoying (not being able to hit enter), including users who have changed their search engine - hence the setup tag
2019-04-27 16:12:25 +00:00
e6017af4bd 3 disk cache prefs
see 053808ba97
2019-04-27 14:06:48 +00:00
053808ba97 1001: remove dead wood
- these are not needed, you can view your cache in about:cache, or look at your `profile/cache2` folder (at least for portable Firefox), the remaining pref is enough to achieve the desired result
- browser.cache.disk.smart_size.first_run is set internally (for me it got automatically reset to modified false)
- the other two prefs are just more things for users to have deal with if they want to use disk cache
2019-04-27 14:03:02 +00:00
2d0182ce6e 1001: add setup tag
- remove tag from section header (chrome)
- add tag to pref (perf)
- mention that we clear on close
2019-04-27 13:53:02 +00:00
98f65da430 remove dead setup tags 2019-04-27 07:33:30 +00:00
6a0c44d0a4 2517: should be warning, not setup
If it's inactive then it's a warning. We can still go through the js and add setup-harden tags for a few inactive items, which I will do
2019-04-27 07:03:28 +00:00
882d25f725 2610: SVG: should be warning, not setup 2019-04-27 07:00:40 +00:00
c3210d1be9 1241: insecure passive: add setup tag 2019-04-27 06:55:58 +00:00
d4f7590c83 2212: add setup tag
- doesn't need any more than that. users can fiddle with it to find what works for them: I'm sure this breaks a lot of website "features"
2019-04-24 08:39:11 +00:00
d6ccf7ba64 0860 form history: add setup tag / warning
- Used setup-web since it relates to actual web pages, even though it doesn't break them
- Added the tag because it's an item that is likely to get attention / troubleshooting
- Added a warning tag to make the risk more apparent.
- Slight edit to the 2803 references
2019-04-24 08:12:31 +00:00
0922215670 1840 openh264 -> inactive
WebRTC is already disabled
2019-04-24 07:46:47 +00:00
f849e1c602 WOFF2 -> inactive 2019-04-24 06:39:59 +00:00
986c900193 RFP tidy up 2019-04-23 05:50:35 +00:00
b8367959da mathml: a better test 2019-04-23 05:33:06 +00:00
b05cfc32de HTTP2 tweak 2019-04-23 04:04:22 +00:00
358ddfdfce pdfjs - add setup tag 2019-04-22 15:38:26 +00:00
8a68fc48c5 pdfjs.enableWebGL 2019-04-22 15:21:16 +00:00
87959d621c 2010: remove pdf webgl
it's default false, and I want to simplify webgl 2010+2012
2019-04-22 15:20:16 +00:00
8b07fd57d0 canvas.capturestream.enabled 2019-04-22 14:35:51 +00:00
4989928c1e 2026: remove (canvas.capture*)
Disabled back when first added as a stop gap measure, never checked on since. TB has this at true, so I think we can get rid of it
2019-04-22 14:34:07 +00:00
c2775a3441 0860 form history info, closes 2019-04-22 14:15:58 +00:00
50d31a7aa2 2701 cookies add setup-web tag 2019-04-22 13:31:15 +00:00
9fbe3080c5 2651: add setup-chrome tag 2019-04-22 13:28:07 +00:00