3 ms·

Isn't this exactly the kind of user-hostile behavior open source is supposed to prevent? Apologies if this is a naive question, but how hard would it be to dele

Isn't this exactly the kind of user-hostile behavior open source is supposed to prevent? Apologies if this is a naive question, but how hard would it be to delete the parts of the release version of the Firefox source code that pertain to checking signatures for add-ons and recompile it?

zaarn 8y ago
You don't need to delete anything, simply use the developer version, nightly or an unbranded version. Unbranded is a compile option. It's not really user hostile either, from what I gather one of the volunteers who check addons has flagged the addon for violating the ToS. They may have had that impression and the author can bring it up elsewhere (there is plenty of contact points for addon authors) or resubmit the addon and see if another volunteer waves it through.
kbumsik 8y ago
> Isn't this exactly the kind of user-hostile behavior open source is supposed to prevent? What part of behavior is user-hostile?
- Karunamon 8y ago
  Preventing the user from installing whatever they choose, for starters.
  - kbumsik 8y ago
    > for starters. It is not only for starter but for the whole platform ecosystem. It is not even user-hostile. It is just to prevent "Nah forget Firefox add-on market, just install this file" fragmentation. Firefox add-on platform is already much smaller than Google chrome (of course). I wouldn't be happy if the market got even smaller because of the fragmentation. And Firefox already allows us to install whatever we want in dev/nightly version, for hackers. So I don't see any problems here.
    - anoncake 8y ago
      What? There is no requirement to offer your add-on on AMO.
      - Karunamon 8y ago
        No, just a requirement that you submit your addon for signing, submit to a separate agreement[1], and their policies[2] (which has separate sub-politics about data usage), regardless of whether you offer it on AMO or not. [1]: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/AMO/Policy/Agreement https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/AMO... [2]:https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/AMO/Policy/Reviews https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/AMO...

zaarn 8y ago

You don't need to delete anything, simply use the developer version, nightly or an unbranded version. Unbranded is a compile option. It's not really user hostile either, from what I gather one of the volunteers who check addons has flagged the addon for violating the ToS. They may have had that impression and the author can bring it up elsewhere (there is plenty of contact points for addon authors) or resubmit the addon and see if another volunteer waves it through.

kbumsik 8y ago

> Isn't this exactly the kind of user-hostile behavior open source is supposed to prevent? What part of behavior is user-hostile?

Karunamon 8y ago
Preventing the user from installing whatever they choose, for starters.
- kbumsik 8y ago
  > for starters. It is not only for starter but for the whole platform ecosystem. It is not even user-hostile. It is just to prevent "Nah forget Firefox add-on market, just install this file" fragmentation. Firefox add-on platform is already much smaller than Google chrome (of course). I wouldn't be happy if the market got even smaller because of the fragmentation. And Firefox already allows us to install whatever we want in dev/nightly version, for hackers. So I don't see any problems here.
  - anoncake 8y ago
    What? There is no requirement to offer your add-on on AMO.
    - Karunamon 8y ago
      No, just a requirement that you submit your addon for signing, submit to a separate agreement[1], and their policies[2] (which has separate sub-politics about data usage), regardless of whether you offer it on AMO or not. [1]: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/AMO/Policy/Agreement https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/AMO... [2]:https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/AMO/Policy/Reviews https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/AMO...