Thanks for fixing this. Also give the devs award or something for have stay up all night to fix this and deal with the shitshow of people complaining from all corner of the internet.
Conversation
Not a fan of crunch to fix this. Why I'm upset is that it was known THREE YEARS ago that this could happen, and not fixed.
Quote Tweet
Oh wow. So, the screw-up with cert expiration breaking Firefox addons has a witty alias "armagadd-on-2.0" on their Bugzilla.
And the person reporting the "1.0" instance says, in the *very first line*:
"If I download an add-on it should continue to work unless it is blocklisted"
Show this thread
2
3
44
Them having known this for 3 plus years you have to assume this was planned. Some money exchanged hands to slow the patch. I am fairly certain, somewhere, compensation for the continued outage is taking place. The Ad Blockers were working to well, donations must be down.
2
1
Is there any other alternative to Firefox? I am not using Chrome. You cant pay me to sell my data to them. And heck if im touching Opera. What other browsers are there who havent sold out to the globalists? I legit want out of this spy watch-net!
3
Chromium, which is the open source build of Chrome but without some of the telemetry by default, EMEs (so no Netflix), no proprietary codecs like MP3 (solved on most Linux distros), or Flash. It works pretty well on Linux, but honestly Firefox is the best suggestion.
2
Chromium has the awful Google account login integration with browser login (i.e. access GMail from it and your browser gets logged in too) as far as I know, which is pretty much a show-stopper. Unless you or your distro patches that out when building.
2
1
They made that a toggle in the standard privacy settings, including in Chrome:
Allow Chromium sign-in
By turning this off, you can sign in to Google sites such as Gmail, without signing in to Chromium
It started out with only a hidden flag for developers in chrome://flags.
2
1
2
I think it was fixed ~18 weeks later in the next release, or maybe it was 36 weeks if it took 2 releases. I wouldn't necessarily say it's fixed, since all they changed is exposing a user-facing setting. I think it still defaults to tying Google login to the browser profile.
1
1
It used to be that signing into Google vs. signing into Chrome (or Chromium) was completely separate. The main (only?) feature offered by signing into the browser is the option to enable sync and toggle which forms of data / settings get synced across browsers via the account.
2
1
I think the new user-facing toggle controls whether signing into the browser can happen at all. If you choose to sign into the browser, I do think it's still going to treat that as a Google session within the content too, so it's still unified but you can choose not to do it now.