Git/firefox-user.js
1
0
Fork 0
mirror of https://github.com/arkenfox/user.js.git synced 2024-11-22 10:31:40 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updated 4.1 Extensions (markdown)

Thorin-Oakenpants 2020-12-31 00:12:47 +00:00
parent e0c1019c2e
commit fcb0bda67c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
4.1-Extensions.md

@ -24,9 +24,9 @@ This list covers privacy and security related extensions only. While we believe
--- ---
### :small_orange_diamond: Extensions (maybe) ### :small_orange_diamond: Extensions (maybe)
* [uMatrix](https://addons.mozilla.org/firefox/addon/umatrix/) <sup>✔ [Privacy](https://github.com/gorhill/uMatrix/wiki/Privacy-policy)</sup> | [GitHub](https://github.com/gorhill/uMatrix) * [uMatrix](https://addons.mozilla.org/firefox/addon/umatrix/) <sup>✔ [Privacy](https://github.com/gorhill/uMatrix/wiki/Privacy-policy)</sup> | [GitHub](https://github.com/gorhill/uMatrix)
- No longer maintained. Everything uMatrix did can be covered by prefs or other extensions. However, it is/was already very stable. Use it as long as it works for you (assuming you know how to - No longer maintained. Everything uMatrix did can be covered by prefs or other extensions: use uBlock Origin for the content blocking. However, uMatrix was very stable. Use it as long as it works for you... except that's risky, because how do you *know* it's working properly?
* [HTTPS Everywhere](https://addons.mozilla.org/firefox/addon/https-everywhere/) <sup>✔ [Privacy](https://www.eff.org/code/privacy/policy)</sup> | [GitHub](https://github.com/EFForg/https-everywhere) * [HTTPS Everywhere](https://addons.mozilla.org/firefox/addon/https-everywhere/) <sup>✔ [Privacy](https://www.eff.org/code/privacy/policy)</sup> | [GitHub](https://github.com/EFForg/https-everywhere)
- If you're using HTTPS-Only mode (usable since Firefox 83), then this is basically redundant, especially as more of the web turns to secure context - If you're using HTTPS-Only mode (usable since FF83), then this is basically redundant, especially as more of the web turns to secure context
* [CanvasBlocker](https://addons.mozilla.org/firefox/addon/canvasblocker/) <sup>✔ [Privacy](https://addons.mozilla.org/firefox/addon/canvasblocker/privacy/)</sup> | [GitHub](https://github.com/kkapsner/CanvasBlocker) * [CanvasBlocker](https://addons.mozilla.org/firefox/addon/canvasblocker/) <sup>✔ [Privacy](https://addons.mozilla.org/firefox/addon/canvasblocker/privacy/)</sup> | [GitHub](https://github.com/kkapsner/CanvasBlocker)
- **DO NOT** use `Screen API` or `Navigator API` protections with RFP - **DO NOT** use `Screen API` or `Navigator API` protections with RFP
- `Window` is protected in the user.js since FF82+ (`privacy.window.name.update.enabled`) - `Window` is protected in the user.js since FF82+ (`privacy.window.name.update.enabled`)