[META] Browser extensions issues

[Mikaela]

• https://github.com/privacytoolsIO/privacytools.io/issues/341 - Add containers for Firefox
• https://github.com/privacytoolsIO/privacytools.io/issues/1313 - Suggestion: Privacy Spy
• https://github.com/privacytoolsIO/privacytools.io/issues/1292 - Suggest HTTPS Everywhere EASE mode and note that many extensions may conflict due to CSP handling in Firefox
• https://github.com/privacytoolsIO/privacytools.io/issues/1326 - Decentraleyes needs additional configuration when used together with HTTPS Everywhere (on Chromium) or a lot of other content blockers on any browser
• https://github.com/privacytoolsIO/privacytools.io/issues/1327 [privacytoolsIO/privacytools.io] 🌐 Website Issue | Add more categories for Browser Add-ons (#1327) #1346 - Browser addons needs more categories
• https://github.com/privacytoolsIO/privacytools.io/issues/1532 - about:config warning changes in Firefox 70
• https://github.com/privacytoolsIO/privacytools.io/issues/1779 - replace Decentraleyes with LocalCDN?
• https://github.com/privacytoolsIO/privacytools.io/issues/1786 - Joining CanvasBlocker to the Add-Ons List

[jasonbrown1965]

Minor update for add-ons page:

Step 2 under about:config Preparations currently reads:
2. Press the button "I'll be careful, I promise!"

In FF 70.01, the text now reads:
"I accept the risk!"

[dngray]

I'm thinking we should add Temporary Containers and link to this article under the power user section. Mention that Cookie Autodelete is not necessary when using.

I also think CleanURLs is certainly worth adding, typically as people make the mistake of pasting URLs they've visited with those tracking parameters on them.

For the uMatrix description we should describe that you don't need NoScript in addition to uMatrix, if you configure uMatrix to How to block 1st party scripts everywhere by default.

We should also mention for Decentraleyes that might need further configuration if used in conjunction with uMatrix or uBlock.

[Mikaela]

We should also mention for Decentraleyes that might need further configuration if used in conjunction with uMatrix or uBlock.

Alternatively we could consider delisting Decentraleyes?

• https://forum.privacytools.io/t/discussion-decentraleyes/269/8?u=mikaela

[dngray]

Likely LocalCDN requires the same kind of configuration.

[Mikaela]

Yes, and it appears that since I previously looked into it (in the forum), LocalCDN has added a generator for what to put into µMatrix/µBlock configuration.

• https://gitlab.com/nobody42/localcdn/-/wikis/Rule-sets-for-uMatrix-and-uBlock-Origin-users

My suggestion/intent was to delist Decentraleyes without replacing it, but I guess now LocalCDN could be worth considering.

[dngray]

Requires investigation: https://github.com/privacytoolsIO/privacytools.io/issues/1801

[dngray]

Also related https://github.com/privacytoolsIO/privacytools.io/issues/927

[dngray]

I think we we should just remove localcdn/decentraleyes and encourage first party isolation #1931 (comment)

It's also worth noting LocalCDN does not work on Fenix currently, while Decentraleyes does.

I think cookie autodelete should also be removed, as it doesn't actually work on Fenix. I think we may do away with umatrix as well now that it is unmaintained.