3 ms·

Correct, you can't install unsigned (not approved by Mozilla) extensions/add-ons in the main Firefox release. You have to use insecure/crashy versions (develope

Correct, you can't install unsigned (not approved by Mozilla) extensions/add-ons in the main Firefox release. You have to use insecure/crashy versions (developer*) or you can dig deep and find the unbranded builds of Firefox and manually download and unpack them for every single update (they have updates disabled). It's tedious but I do it. The ESR releases of FF main don't allow unsigned add-ons. You may be using a custom user freedom respecting build Debian specifically negotiated with Mozilla to allow in it's repositories? *The developer version is literally the alpha release, later renamed aurora, later named developer. It is not acceptable to use an alpha release as a main driver for security and stability reasons. You're right about disabling DRM though. That's not a deal breaker the way it's implemented.

JoshTriplett 3y ago
Outdated information, sorry: some reports suggest that at one point they had disallowed it on standard builds but allowed it on ESR, but that doesn't seem to be the case anymore. So, yes, you have to use a developer version, or a packaged version. That said: What extensions, exactly, do you want to use on Firefox that aren't shipped on AMO? Other than the development of extensions themselves (for which it makes sense to use a developer version of Firefox), what is the use case?
- superkuh 3y ago
  For me it's not so much about which extensions but my ability to edit the extensions to fit my needs. Little tweaks to change appearance or text or or some internal list the extension uses. I do this fairly regularly (maybe once a month?).
ArclightMat 3y ago
> The developer version is literally the alpha release, later renamed aurora, later named developer. It is not acceptable to use an alpha release as a main driver for security and stability reasons. It hasn't been for a long time, Mozilla dropped the Aurora channel in 2017 and rebased Developer Edition off Beta [0]. And as far as I'm concerned, beta is as stable as mainline (on my phone, at least). > The ESR releases of FF main don't allow unsigned add-ons. You may be using a custom user freedom respecting build Debian specifically negotiated with Mozilla to allow in it's repositories? Official documentation says you can still load unsigned extensions on ESR, but you need to enable a flag in about:config first [1]. [0] https://venturebeat.com/business/mozilla-kills-firefox-aurora-channel-builds-will-move-directly-from-nightly-to-beta/ https://venturebeat.com/business/mozilla-kills-firefox-auror... [1] https://extensionworkshop.com/documentation/publish/signing-and-distribution-overview/ https://extensionworkshop.com/documentation/publish/signing-...
- superkuh 3y ago
  I imagine if you use it on $latest OS and the like it's stable. But I can assure you if you're distro is a little older then the lib mismatches make developer edition a crashy experience. I'm glad to hear about [1]. I'll have to try this in ESR myself. Hopefully all my extensions have the extra requirement of an add-on ID set. But I suppose I can edit that in myself for each if not.

JoshTriplett 3y ago

Outdated information, sorry: some reports suggest that at one point they had disallowed it on standard builds but allowed it on ESR, but that doesn't seem to be the case anymore. So, yes, you have to use a developer version, or a packaged version. That said: What extensions, exactly, do you want to use on Firefox that aren't shipped on AMO? Other than the development of extensions themselves (for which it makes sense to use a developer version of Firefox), what is the use case?

superkuh 3y ago
For me it's not so much about which extensions but my ability to edit the extensions to fit my needs. Little tweaks to change appearance or text or or some internal list the extension uses. I do this fairly regularly (maybe once a month?).

ArclightMat 3y ago

> The developer version is literally the alpha release, later renamed aurora, later named developer. It is not acceptable to use an alpha release as a main driver for security and stability reasons. It hasn't been for a long time, Mozilla dropped the Aurora channel in 2017 and rebased Developer Edition off Beta [0]. And as far as I'm concerned, beta is as stable as mainline (on my phone, at least). > The ESR releases of FF main don't allow unsigned add-ons. You may be using a custom user freedom respecting build Debian specifically negotiated with Mozilla to allow in it's repositories? Official documentation says you can still load unsigned extensions on ESR, but you need to enable a flag in about:config first [1]. [0] https://venturebeat.com/business/mozilla-kills-firefox-aurora-channel-builds-will-move-directly-from-nightly-to-beta/ https://venturebeat.com/business/mozilla-kills-firefox-auror... [1] https://extensionworkshop.com/documentation/publish/signing-and-distribution-overview/ https://extensionworkshop.com/documentation/publish/signing-...

superkuh 3y ago
I imagine if you use it on $latest OS and the like it's stable. But I can assure you if you're distro is a little older then the lib mismatches make developer edition a crashy experience. I'm glad to hear about [1]. I'll have to try this in ESR myself. Hopefully all my extensions have the extra requirement of an add-on ID set. But I suppose I can edit that in myself for each if not.