You must log in or # to comment.
Not blaming Mozilla for this specifically but since they’re architecture is centralized, they are at the whim of centralized governments who want things to be changed.
So by designing systems, where they are the central authority, they are vulnerable to exactly this happening again and again and again
It’s actually a bit more complicated than that:
- Mozilla centrally signs every add-on—but the add-ons in question are still signed by Mozilla
- Mozilla runs a centralized distribution platform but you can self-host your add-on if you want and you have the option to use a custom update URL—the add-ons in question are still hosted by Mozilla, however, they are geo-blocked in the country that counts
Roskomnadzor probably has something to do with it.