Extension Criteria

[ghost]

I think it would be helpful to lay out what criteria we should have for browser extensions. Here's my tentative list:

1. It must do something that's only possible with the extension (this has precedent with the TOS;DR extension, which was convenient but the functionality could be utilized on their site), since any extra extensions means greater fingerprinting potential and greater attack surface.
2. It must be recommended on the arkenfox wiki, since I think ideally pg should aim to follow their guidelines as closely as possible.
3. It must be recommended by Mozilla, that way we know it has been reviewed and deemed safe.
4. It must not replicate the functionality of another extension that is already recommended; in this case, it should be decided between the new one and the old one.

I'm open to any suggestions and improvements, this is just a very rough draft.

[ph00lt0]

I do agree with point 1 but certainly not with 2 and 3. We shouldn't be limiting ourselves to evaluation of other projects. And yes it would be good to have some criteria defined.

[ghost]

Ok removing number 2 I can get behind. I still think making sure that the extension has been reviewed by Mozilla is a good idea though for security.

[ph00lt0]

Oh that's cool, I actually didn't know that those were reviewed on security by Mozilla.
Link for those like me: https://support.mozilla.org/en-US/kb/add-on-badges

[ph00lt0]

Yeah it might be of value, I am just afraid that it would limit a new extension from being listed which actually could help. It would be silly if we wouldn't be able to list it because of this term. I am very split on this

[ghost]

I don't think new extensions should be listed though, they should have to prove that they will be actively developed for a long time and that they are indispensable tools.

[dngray]

I think in general this will be best done on a case-by-case basis. Adblocking is about the only arguable context where privacy is gained through an extension.

I would be happy to remove adblockers if the functionality became part of the browser and worked as well.

[ph00lt0]

What about Mullvad Privacy Companion? I can see some advantages here, especially if they integrate a per domain based solution as is planned.

https://mullvad.net/en/blog/2022/3/22/mullvad-privacy-companion-now-open-source/