Oh wow, thank you so much for this. I've been trying to troubleshoot this for hours but because my browser didn't work I never thought of checking HN to see if other people had this as well.
Another score for automatic updates I guess.
Another score for automatic updates I guess.
FWIW I've tried every documented setting, "enterprise" policies, etc. to prevent automatic updates in FF, but nothing seems to stick.
That's s private installation, a company-wide centrally managed might work differently ... but companies normally want to control updates too.
The goal is not to ostracize automatic updates, but to have faster fixes.
Or to separate security updates from feature updates, but I think this ship has long sailed for modern browsers.
That would be my preferred solution. But yes, as you say, that ship has sailed. No reason why it couldn't sail back though.
Maintenance cost.
Multiplying the number of parallel maintenance tracks and associated support costs is not “no reason”.
User is the one who must choose update policy. If user is choosing to not update then it's their own problem and no manufacturer has the right to deside otherwise.
https://support.mozilla.org/en-US/kb/switch-to-firefox-exten...
Even if you don't update your browser, the world updates around it
> Telemetry has nothing to do with this, it just happens to be one of the first services with H3 load balancer.
If telemetry really had "nothing to do with" the bug, then the fact that telemetry "just happens to be one of the first services with H3 load balancer" wouldn't trigger the bug.
The question isn't whether "backend services" forms the conceptual essence of the problem - I think we all agree it doesn't.
The question is whether it "happens to be" triggered by backend services.
Edit: reading further comments it occurred to me that maybe I'm not affected because I'm not sending any data to Mozilla so I don't hit their HTTP3 load balancer.
Go interview people Mozilla. Less analytical data but you'll end up knowing your users.
I would like to see any source that may exist on it having been silently re-enabled. I know telemetry is anonymized and totally harmless or whatever, but re-enabling it behind my back would feel like such a breach of trust.
Thanks anyone in this thread who helped!
Very frustrating this. Fortunately it isn't a Tuesday or I would have been ready for murder by now.
As I instinctively was already blaming out IT dept for breaking Firefox for some security theater reason I was glad I found the real issue quickly, otherwise I might just have accidentally dropped my laptop out the window