mconnormoz
commented
2 years ago The current feature is relatively limited, and built with the specific use case of implementing legally required blocks for a given add-on. The copy and HTTP usage is narrowly scoped to HTTP 451. We're not going to expose that specific implementation to developers at this time.
Bigger picture, this is a capability that has a number of legitimate use cases, so we're going to look into this as a part of our developer support roadmap for the second half of the year.
There's a long list of questions we'll need to answer, including but not limited to:
- What do we want to allow blocking?
- Discovery & install? What about local installs?
- Updates? (e.g. existing clients)
- Any usage at all? (do we block loading/usage? force uninstalls?)
- Who decides on restrictions?
- Is this allowed for specific use cases only, or any reason?
- Does this require admin approval or can devs do it themselves?
- How do we present reasons to an end user?
KevinMind
Developers may want to restrict the distribution of their extensions in certain regions, in a similar way it is done on the Chrome Web Store, Microsoft Store and App Store. The feature appears to be already implemented and available to AMO admins, it would be great to also make it available to developers.
┆Issue is synchronized with this Jira Task