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

1299 Commits

Author SHA1 Message Date
5bd5f6b28e 0912: HTTP Auth sub-resources () 2018-12-18 01:41:37 +13:00
55c2cacbce 0335: toolkit.telemetry.coverage.opt-out () 2018-12-17 22:43:45 +13:00
4badc42879 0105b: kill snippets endpoint
it's too hard to follow AS changes, and work out if disabling showing items (basic toggling of show/hide sections etc) actually stops downloading a localized local copy etc. For items we actually want to block, let the endpoint slaughter begin.
2018-12-17 09:36:26 +00:00
6946a01232 Update troubleshooter.js 2018-12-17 08:19:14 +00:00
da80e39064 0105s: description s/be self explanatory
when filtered and 0105a is not shown, AS doesn't mean anything
2018-12-16 17:37:42 +00:00
c1d6d81528 add PERF tags to wasm, asm.js, closes 2018-12-16 14:10:32 +00:00
d5ece0f6f4 1700s: revamp Containers header () 2018-12-14 07:05:43 +00:00
f6ea20a8b0 0335: Telemetry Coverage endpoint
let's just coverage-our-ass on this one

While I don't mind telemetry (development needs meaningful feedback to better the product), and I trust the data is not PII, and/or anonymized into buckets etc (you can check this you know), and I understand this one needs to be outside the Telemetry pref in order to gather the one-time ping ... and I trust Mozilla's motives ... I'm starting to get a little annoyed at the non-stop incessant increasing telemetry bullshittery and ass-fuckery around sending data home, and the lengths some Mozilla devs will go to, to hide this info (hidden prefs, access denied tickets to hide discussion of what should be public, and even **not even adhering to their own documentation**).

I will also be killing as many Activity Stream endpoints as well - as long as they are in line with our js - pocket, snippets, onboarding etc. And I will add those from personal as inactive for end-users - eg cfr
2018-12-13 17:28:16 +00:00
645492e82f grammar, case, etc, closes
thanks @Just-me-ghacks
2018-12-14 04:49:50 +13:00
15c68dc344 disable System Add-on updates ()
remember the new Coverage Telemetry shit? with a **hidden** opt-out pref? guess what, they are already collecting for 3 months ...

https://bugzilla.mozilla.org/show_bug.cgi?id=1487578 - **3 months ago**: "I see data coming in that looks reasonable"

guess what else ...

"It has also replaced the previous version that was there (from bug 1480194)" and oh, surprise surprise, 1480194 is ACCESS DENIED!

they're not just using private tickets to hide security critical information from potential hackers and blackhats, no they also use it to hide shady AF things. Things that they fully know are shady as fuck and that they absolutely know a lot of people would not like. There's simply no other reason why they'd do that

but wait, that's not all. If you think an opt-out pref that 99% of people wouldn't know about even if it showed up in about:config BUT ALSO HAPPENS TO BE HIDDEN is kind of questionable, well ... the system addon that they use for this shit apparently looked or still looks for `toolkit.telemetry.coverage.opt-out` [1] instead of `toolkit.coverage.opt-out` as their documentation [2] claims

[1] https://github.com/mozilla/one-off-system-add-ons/pull/131/files#diff-6e0cbf76986d04383ccb32a29ef27a7aR25
[2] https://hg.mozilla.org/mozilla-central/file/tip/toolkit/components/telemetry/docs/data/coverage-ping.rst#l32

It's time to opt out of all that shit for good. Disable system addon updates and kill it at the root

> In FF61 and lower, you will not get any System Add-on updates except when you update Firefox

on its own that's not true. You will get SA updates unless you disable app update checks + auto install. Let's just remove that as well.
2018-12-14 03:21:57 +13:00
04b797f1aa 0209: remove trailing space
@Just-me-ghacks 💋
2018-12-13 11:14:44 +00:00
e60abd6c44 64-beta v64.0-beta 2018-12-12 17:17:33 +00:00
d55b8176ad dyslexia and/or dementia 2018-12-12 16:52:12 +00:00
31adbba774 5000s: disable CFR 2018-12-12 16:34:27 +00:00
3c247a2c5b Update ghacks-clear-[removed].js 2018-12-12 13:22:58 +00:00
879f0abf28 2201: more garbage 2018-12-12 13:21:24 +00:00
d97d0ec0f5 media.peerconnection*
covered by user_pref("media.peerconnection.enabled", false);
2018-12-12 13:09:03 +00:00
3916e38681 taking out the garbage () 2018-12-13 02:02:38 +13:00
51ac69874b 0105* remove // has setting 2018-12-12 11:58:48 +00:00
2d956d04f3 move 1260 to 122x ()
* move 1260 to 122x

"disable or limit SHA-1 certificates" is about certs, not ciphers.
Because CERTS is 1st in the title I moved it to the 1st item there because it's arguably also the most important of the lot (and renumbered the rest)
We can also drop HSTS from the subgroup title because there's nothing HSTS left atm.
2018-12-13 00:52:49 +13:00
9d6bfb650c disable Telemetry Coverage () 2018-12-13 00:29:29 +13:00
ccdd4decf0 Pocket: 0510->0370
Pocket is no longer a System Add-on in FF64+
2018-12-12 08:25:25 +00:00
f0fbfd3086 network.auth.subresource-img-cross-origin-http-auth-allow 2018-12-11 17:44:19 +00:00
88b747ef36 0911: remove it,
it is default false in FF59+
2018-12-11 17:42:19 +00:00
c6ebe36165 1022: resume from crash=>inactive, closes 2018-12-11 17:28:21 +00:00
7684e83aba 0102 add SR info 2018-12-11 17:18:26 +00:00
4f37975566 browser.sessionstore.max_windows_undo 2018-12-11 16:49:38 +00:00
26b874bed7 1020: remove max_windows 2018-12-11 16:43:11 +00:00
61be5ae563 all Deprecations + new ADB extension prefs () 2018-12-12 05:07:28 +13:00
ef1e61ebcd start 64-alpha 2018-12-11 16:05:07 +00:00
205c48d9d3 final 63 release 63.0 2018-12-11 15:49:31 +00:00
0e1b0a4b6e move 0370 to 0105b () 2018-12-12 04:40:29 +13:00
778dc89bb6 2002 WebRTC tests
FYI, the https://www.privacytools.io/webrtc.html test in our wiki is 404, so I gave it a strikethru and added this one. This is also handy for 2001, but do we need to double up on it? We're only disabling WebRTC because of IP leaks, so I don't see the point in testing if WebRTC is disabled.
2018-12-11 00:40:03 +00:00
23733097a9 2302 FF version 2018-12-11 00:13:07 +00:00
71a2d393f3 minor wording changes () 2018-12-11 11:23:00 +13:00
74ebacc0dd obey rules for [setting] tag location
all setting tags must be between `/* ... ***/`
2018-12-10 19:52:48 +00:00
45e3b3a0e0 2682: put correct version back
0a67cdec8b (comments)
2018-12-10 19:35:41 +00:00
8172f730d3 Update README.md 2018-12-10 19:26:17 +00:00
5c85e61bb4 4000: remove old FPI notes () 2018-12-10 18:36:07 +00:00
0a67cdec8b cleanups ()
- cleanup of tags placement, order consistency, and to use square brackets (allows usage elsewhere to not get tagged, eg 1402)
- other bits and bobs
2018-12-11 07:18:26 +13:00
b85668c2cd make description & info & notes concurrent 2018-12-08 04:10:13 +13:00
786839ffc1 2701: fix split multi-[notes] 2018-12-06 08:16:01 +00:00
8313f2e01a 1020: fix description
Session Restore cannot be disabled in Normal mode, it is also used internally. FYI: PB Mode does not use Session Restore. The description is still not 100%, as it refers to what is restored, not what is kept in the recovery.jsonlz4 (at least for tabs)
2018-12-06 05:41:25 +00:00
0a87c99a0e 1203: ssl session ids are 24hrs 2018-12-05 20:58:07 +00:00
91fed43fc7 0703 atl-svc, better ref, 2018-12-05 20:36:20 +00:00
74f029566e enforce DOMHighResTimeStamp API
flipped true in FF54: https://bugzilla.mozilla.org/show_bug.cgi?id=1026804 but unsure when the pref itself was introduced. note: other timing prefs were always in 2400's see 4602: [2411] disable resource/navigation timing / 4603: [2412] disable timing attacks
2018-12-04 10:34:02 +00:00
571be93ae0 proper case convention after tags
Can't believe I did this. Out of 32 `[setup*` and  9 `[warning]` tags (excluding the readme), I let one capital letter get past me, the bastard!
2018-12-04 10:26:44 +00:00
11b16c9c6d move PB mode into STARTUP section 2018-12-04 08:51:19 +00:00
c4ec4dbc77 move 0000 to personal
it has zero to do with privacy etc, and in fact most users will only ever encounter it once (and check the box) when they first go to about:config, so it's not even useful as an override or a new profile IMO. This removes one of three numbers that don't have a section
2018-12-04 08:34:36 +00:00
67998eb4af section naming convention consistency 2018-12-04 08:27:52 +00:00