"The Developer Edition and Nightly versions of Firefox will have a setting to disable signature enforcement. 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."
For my main browser that has all the plugins I used to appreciate in Firefox I switched to Pale Moon [1]. On other machines I continue to use Firefox.
Very happy with Pale Moon, works perfect -including all my old plugins- and I'm no longer afraid that features I depend on will stop working because the mozilla dev's decided to try and change firefox into chrome.
If you don't care for tab groups - my experiences with Pale Moon were great! I can imagine it's remained as awesome since I stopped using it (which is when they removed tab groups...)
E:
Also it's totally possible the add-on has been fixed. But I don't remember anyone maintaining it, it was just segmented away from the browser and made into an add-on without development/maintenance. It's possible that has changed and the above issue is no longer relevant.
You are correct that tab groups is offered as an add-on. Had no problem installing it, it even kept all the tabs I had in tab groups in Firefox. For me the transition from Firefox to Pale Moon was very smooth.
[1] http://www.ghacks.net/2015/11/08/mozilla-to-remove-tab-group...
If those two issues have been fixed I'd likely very quickly switch back to Pale Moon.
As an aside, I'm aware FF is removing them as well in the near future. I've already frozen myself on FF 40 for other reasons. Before anyone mentions - I'm aware of the potential security risks of doing so and have decided given my internet browsing habits it is very low risk. Low enough that I don't even consider publicly announcing my use of FF40 to be a significant security threat.
But -if it helps- the tab groups are remembered after I kill firefox from Windows task manager.
Also no problem on updating Pale Moon. But I've got to admit that there was only one update since I switched over to Pale Moon.
https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...
I'm currently running Firefox 43 on Arch Linux:
$ pacman -Q firefox
firefox 43.0-1
with Tree Style Tab 0.16.something from AMO and have `xpinstall.signatures.required` set to `true` (the default, I haven't changed anything).That extension has been clearly signed.
> Firefox 44: Release and Beta versions of Firefox will not allow unsigned extensions to be installed, with no override.
Why are they doing this? It's condescending and insulting. "No, you're too stupid to be allowed to install what you want to."
Now we seem to be nerfing the beast because someone might do stupid things.
I understand why Mozilla and Google have done similar things to restrict extension installation, but can't help but think there has to be a better way for users who know what they're doing.
Browsers are putting a lot of effort into preventing this, they wouldn't do it if they didn't have clear information showing the problem was serious.
1. Fixing the extension "code review" process, which is a mess. Make it be actually automatic 99% of the time and not a big hassle.
2. Implementing non-mandatory signing a long time ago and let that run for at least a year before making it mandatory. (The initial announcement that extension signing was going to happen was Feb 10 2015.)
3. Waiting for at least half a year after making signing mandatory to start even announcing "we will change the API and severely break all non-trivial extensions in the near future".
Right now, I think Firefox has set themselves up to decimate the number of extensions, by telling extension devs they have a mountain of work ahead of them for very little benefit. I can't imagine it will do anything but further reduce the number of users. Not sure what will come off it in the end. As a pentadactyl addict, I'm worried that I'll be on the next LTS release (without signing) for years to come. Either that, or we'll see a fork.
As for requiring signing, from the moz wiki: "The current plan is to have ESR 45 work like 40-42, with a preference that can turn off [signing] enforcement."
Edit: source: https://wiki.mozilla.org/Add-ons/Extension_Signing
The people producing my AV package do just that, 8 hours a day, all year long. How much time does Mozilla's AV coders have? How much practical experience?
IMHO, Mozilla's FireFox team should concentrate on making the browser work fast and smooth. Period. FireFox has been slowly deteriorating for years while they've diddled with cutesy GUI crap.
Too many spoons in the pot.
Also read as "doing the literally impossible (but not really)".
http://danstillman.com/2015/11/23/firefox-extension-scanning...
""" It’s been a maddening discussion, with Mozilla folks repeatedly suggesting that Zotero — a leading research tool put out by a large public research university as a non-profit open-source project and recommended by nearly every university worldwide — will either turn rogue or become an attack vector if we’re allowed to continue releasing it unimpeded as we have for nine years. """
How long until they withhold their signature from an extension which blocks ads from one of their funders, or which supports a political cause they dislike, or are pressured to dislike?
In fact, what assurance at all does Mozilla's signature give me? As far as I can tell, none whatsoever.