Updated 4.1 Extensions (markdown)

4.1-Extensions.md

@@ -65,8 +65,8 @@ These extensions will not mask or alter any data sent or received, but may be us
   - Replacing scripts on CDNs with local versions is not a comprehensive solution and is a form of [enumerating badness](https://www.ranum.com/security/computer_security/editorials/dumb/). While it may work with some scripts that are included it doesn’t help with most other third party connections
   - CDN extensions don't really improve privacy as far as sharing your IP address is concerned and their usage is fingerprintable as this Tor Project developer [points out](https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/22089#note_2639603). They are the [wrong tool](https://en.wikipedia.org/wiki/XY_problem) for the job and are not a substitute for a good VPN or Tor Browser. Its worth noting the [resources](https://git.synz.io/Synzvato/decentraleyes/-/tree/master/resources) for Decentraleyes are hugely out of date and would not likely be used anyway
 * Temporary Containers, Cookie extensions
-  - ❗️ Sanitizing in-session is a false sense of privacy. Extensions may lack APIs or application of them, and it does nothing for IP tracking. Even Tor Browser does not sanitize in-session e.g. when you request a new circuit. A new ID requires _both_ a new sanitized session _and_ a new IP. The same applies to Firefox.
   - Redundant with [Total Cookie Protection](https://blog.mozilla.org/security/2021/02/23/total-cookie-protection/) (dFPI) or FPI
+  - ❗️ Sanitizing in-session is a false sense of privacy. Extensions may lack APIs or application of them, and it does nothing for IP tracking. Even Tor Browser does not sanitize in-session e.g. when you request a new circuit. A new ID requires _both_ a new sanitized session _and_ a new IP. The same applies to Firefox.
   - Note: If you want multiple and/or concurrent logins to the same site, use Multi-Account Containers
 
 ---