Though its worth noting that we do not need reasons to expect our privacy being respected. And this issue is not just about me and my needs, but about user liberties, so please refrain from making it personal.
> Also why can't a user take the code for your extension, create an account on the add-on marketplace and privately get it signed for themselves. It's a multistep process but works.
No, it does not work, as the maintainer of Page Translator can attest.
This change is hostile to users and concentrates power in the hands of the browser vendor. Consider that they are making third-party extension stores impossible.
Ouch. I'm generally in favour of having add-ons signed, but I do have an extension that injects an external script into the browser and web pages - for a completely non-nefarious use case.
I do understand the security risk and why they'd block it, but I'm not looking forward to the day my extension is no longer flying under the radar and gets pulled.
Edit: Of note is that the Chrome web-store does allow my extension, but requires a multi-week review every time I upload a new version. Somehow they're fine with the remote code, even though it could change after their review.
Though its worth noting that we do not need reasons to expect our privacy being respected. And this issue is not just about me and my needs, but about user liberties, so please refrain from making it personal.
> Also why can't a user take the code for your extension, create an account on the add-on marketplace and privately get it signed for themselves. It's a multistep process but works.
No, it does not work, as the maintainer of Page Translator can attest.
https://github.com/jeremiahlee/page-translator/issues/26
This change is hostile to users and concentrates power in the hands of the browser vendor. Consider that they are making third-party extension stores impossible.