3 ms·
Publishing a Mozilla-signed XPI outside of AMO is a breach of ToS, and can lead to being removed from the AMO.
by ErikBjare 2y ago
Publishing a Mozilla-signed XPI outside of AMO is a breach of ToS, and can lead to being removed from the AMO.
- phoe-krk 2y agoSo posting the contents of my ~/.mozilla/firefox/default/extensions/ on GitHub is going to remove all of them from the store? Goodness, I wonder why no one thought of that until now.
- ErikBjare 2y agoYeah sorry I used imprecise language see: https://news.ycombinator.com/item?id=40766705 https://news.ycombinator.com/item?id=40766705
- cbsks 2y agoSource? I’m not aware of that restriction. Self-hosting xpi files is definitely allowed, and all xpi files are signed by Mozilla. https://extensionworkshop.com/documentation/publish/self-distribution/ https://extensionworkshop.com/documentation/publish/self-dis...
- ErikBjare 2y agoThey threatened me here: https://github.com/orgs/ActivityWatch/discussions/818#discussioncomment-4254275 https://github.com/orgs/ActivityWatch/discussions/818#discus... See https://extensionworkshop.com/documentation/publish/signing-and-distribution-overview/#post-submission-review https://extensionworkshop.com/documentation/publish/signing-... My previous statement was overly broad, but the restrictions do apply to rejected xpis.