[CONTENT-CHANGE] Privacy Respecting Software > Browser Extensions > Provider

[atomGit]

given our previous exchange regarding Firefox, i might suggest cleaning up/removing/rewording the following extensions (for FF specifically... i don't know, nor care, about chrome)

this is assuming a privacy/security user.js is being used (arkenfox)...

• Privacy Badger - raises entropy
• HTTPS Everywhere - not needed
• Firefox Multi-Account Containers/Temporary Containers - there are use cases for these, but for the average person, probably not ??? fingerprinting and isolation is covered by RFP and ETP/dFPI
• Canvas Fingerprint Blocker - covered by RFP
• First Party Isolation - obsolete - replaced by ETP/dFPI - no ext. needed
• LocalCDN/Decentraleyes - still useful speed-wise, but FF now strips some of the identifying info from these requests i'm told, plus ETP/dFPI isolates this stuff
• Vanilla Cookie Manager - probable useless for most people, plus it hasn't been updated in 7 years (there are better storage managers, but all are largely obsolete) - handled with ETP/dFPI
• Privacy Essentials - this could possibly raise entropy - personally not a fan of fluff like this, plus the code would have to be checked, plus much/all of this is handled by FF, arkenfox, RFP, dFPI - less is more
• Self-Destructing Cookies - same opinion as Vanilla Cookie Manager
• Site Bleacher - not needed - ETP/dFPI, RFP
• User Agent Switcher - raises entropy, though there are some instances where one might want to spoof the UA (note that very few of these "spoofers" address the JS UA)
• PrivacySpy - looks like it may be injecting into pages, not sure - also it's easy to detect crap privacy policies... the page has a scroll bar :)

  "web_accessible_resources": [
      "icons/privacyspy-96-dark.png"
  ]

• HTTPZ - as mush as like the work by @claustromaniac, this is no longer needed
• Track Me Not - that's a no-no - covered by RFP, ETP/dFPI
• AmIUnique Timeline - hmmm... a fluff piece i think, plus many/most fingerprint detection sites don't work properly at all according to the arkenfox crew (pants)
• Netcraft Extension - i'm skeptical - first of all, i think anyone that cares about privacy is going to be nuking JS globally (uBO anyone?) and allowing per-site - potentially odd and conflicting privacy policies here and here

this caught my attention...

The Extension collects the following information:

Web sites (not URLs) visited...
Where a web site loads malicious JavaScript...
The Extension does not collect any personal information except that described above. In particular, we do not collect personal information which can identify the browsing habits of individual users.

and then...

You have a right to access the personal information held about you. To obtain a copy of the personal information we hold about you, please mail us at toolbar@netcraft.com.

how would they know how to correlate PII with a user if they collect none? interesting

[atomGit]

maybe it'd be best/easiest just to add a note regarding the most of above... like 'don't use these if using arkenfox'

in that case the list of candidates for removal changes ...

• HTTPS Everywhere
• First Party Isolation
• Vanilla Cookie Manager - needs to be replaced with something better like Cookie AutoDelete
• HTTPZ

[Lissy93]

I'm moving the software section to a separate repo, so I can better manage the two lists. So I'll address this, and your other issues this week :) Sorry for the long delay, everything in life always seems to kick off at the same time..