You don’t have to log in or sign up to read it. A good thing if in fact it is “solved”…I also run Debian on one of my machines and as of about 2 PM this afternoon they had an alert and update for Firefox-esr…given that we had the broken update some 24 hours before that I found the esr update interesting as well…wonder if it was part of the same update cycle that got us the garbage it did…Īlso read the twitter thread put here only thing I was able to discern from it is ' restart ya browser'… someone asked “how many times”…there was no technical information on the Twitter feed at least that I found…ĮDIT- for anyone so curious reddit r/firefox - PSA: Solution for Firefox not working right now.ħ30 votes and 405 comments so far on Redditĭon’t worry, the article linked above is free and publicly available for all interested readers. So if it appears that I am a little “touchy” about things like browsers and IP Table firewalls and security and keeping machines updated, I am. I also live in Ecuador where(at least where I live) the server techs at the ISP dont know the difference between megabits and megabytes- wild west. Not trying to be difficult but I use my machines for financials…crypto, derivatives, banking and so forth. So what does it mean that the problem is “solved”…does that mean we are again operating with the safer HTTP3? Or with the change to about:config we are operating with HTTP2? I tried using Google Translator to make sense of it but the website wants one to log in no? Thanks for posting the article Piscatorius.

Glitches to mozilla thunderbird update