4 ms·

I use several small add-ons I wrote myself. Why should I have to get Mozilla's approval before I can install my own damn add-ons? One of them executes processes

I use several small add-ons I wrote myself. Why should I have to get Mozilla's approval before I can install my own damn add-ons? One of them executes processes and I'm 99% sure it'll fail the automated review. EDIT: It passed the automated review, but my point stands. If I wrote the code, then you can be damn sure I trust it.

atopal 11y ago
> I use several small add-ons I wrote myself. Why should I have to get Mozilla's approval before I can install my own damn add-ons? Mozilla has to balance the needs of several hundred million users, who are being attacked by malware every day, with the needs of people who write their own add-ons. Is it really that difficult to see it from that perspective? And it's not like you have no options now. You can either use the developer edition or the special release version where this feature is disabled.
- Sir_Cmpwn 11y ago
  They've always catered to the hacker perspective, too. Why take out the about:config flag? How about letting me trust my own certificate, instead of just AMO's? What about running AMO alternatives?
  - atopal 11y ago
    Did you not read the blog post? You can use the dev edition or the special release and beta version that don't have this limitation. Nobody is forcing you to live with this limitation. If this was done as an about:config flag it could easily be changed by an add-on too.
    - Sir_Cmpwn 11y ago
      I did read the blog post. It says I have to use a less stable (beta) or less customizable (dev edition) version of Firefox to avoid this burden.
      - soapdog 11y ago
        Dev Edition is not less customizable... its just Firefox with a new theme and more bleeding edge dev tools which you should be using to develop addons anyway.
        Sir_Cmpwn 11y ago
        The theme is the problem I'm referring to.
        djent 11y ago
        The cool thing about themes is that you can change them. Developer Edition just comes with a different default theme.
        Sir_Cmpwn 11y ago
        For some reason I thought you couldn't change it. That's fine, then.
        soapdog 11y ago
        Not only you can download a new theme but you can also develop a whole new one if you'd like.
      - atopal 11y ago
        From https://wiki.mozilla.org/Addons/Extension_Signing https://wiki.mozilla.org/Addons/Extension_Signing "What are my options if I want to install unsigned extensions in Firefox? The Developer Edition and Nightly versions of Firefox will have a setting to disable signature checks. There will also be special unbranded versions of Release and Beta that will have this setting, so that add-on developers can work on their add-ons without having to sign every build."
        Sir_Cmpwn 11y ago

atopal 11y ago

> I use several small add-ons I wrote myself. Why should I have to get Mozilla's approval before I can install my own damn add-ons? Mozilla has to balance the needs of several hundred million users, who are being attacked by malware every day, with the needs of people who write their own add-ons. Is it really that difficult to see it from that perspective? And it's not like you have no options now. You can either use the developer edition or the special release version where this feature is disabled.

Sir_Cmpwn 11y ago
They've always catered to the hacker perspective, too. Why take out the about:config flag? How about letting me trust my own certificate, instead of just AMO's? What about running AMO alternatives?
- atopal 11y ago
  Did you not read the blog post? You can use the dev edition or the special release and beta version that don't have this limitation. Nobody is forcing you to live with this limitation. If this was done as an about:config flag it could easily be changed by an add-on too.
  - Sir_Cmpwn 11y ago
    I did read the blog post. It says I have to use a less stable (beta) or less customizable (dev edition) version of Firefox to avoid this burden.
    - soapdog 11y ago
      Dev Edition is not less customizable... its just Firefox with a new theme and more bleeding edge dev tools which you should be using to develop addons anyway.
      - Sir_Cmpwn 11y ago
        The theme is the problem I'm referring to.
        djent 11y ago
        The cool thing about themes is that you can change them. Developer Edition just comes with a different default theme.
        Sir_Cmpwn 11y ago
        For some reason I thought you couldn't change it. That's fine, then.
        soapdog 11y ago
        Not only you can download a new theme but you can also develop a whole new one if you'd like.
    - atopal 11y ago
      From https://wiki.mozilla.org/Addons/Extension_Signing https://wiki.mozilla.org/Addons/Extension_Signing "What are my options if I want to install unsigned extensions in Firefox? The Developer Edition and Nightly versions of Firefox will have a setting to disable signature checks. There will also be special unbranded versions of Release and Beta that will have this setting, so that add-on developers can work on their add-ons without having to sign every build."
      - Sir_Cmpwn 11y ago