From fcb0bda67cbad97572397a896b507fef0b389c1d Mon Sep 17 00:00:00 2001 From: Thorin-Oakenpants Date: Thu, 31 Dec 2020 00:12:47 +0000 Subject: [PATCH] Updated 4.1 Extensions (markdown) --- 4.1-Extensions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/4.1-Extensions.md b/4.1-Extensions.md index ad7131d..b9ac7ec 100644 --- a/4.1-Extensions.md +++ b/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) * [uMatrix](https://addons.mozilla.org/firefox/addon/umatrix/) ✔ [Privacy](https://github.com/gorhill/uMatrix/wiki/Privacy-policy) | [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/) ✔ [Privacy](https://www.eff.org/code/privacy/policy) | [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/) ✔ [Privacy](https://addons.mozilla.org/firefox/addon/canvasblocker/privacy/) | [GitHub](https://github.com/kkapsner/CanvasBlocker) - **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`)