281–290 of 410 posts
I suggested that data collection should be opt-in since it is (almost) the cause of this issue, and my comment was hidden for "advocacy". https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c11
We are only valued community members when there is a fundraising drive going on. The rest of the year we are just annoying nobodies it seems.
Try to ask for updates on the Tab bar issue if you want to trigger it again.
Earlier quoted context omitted.
As others said, this happened to all kinds of versions, not just 96.
I was perfectly happy with the one that didn't support this 'feature', and automatic updates are what brought it to my system.
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.
Earlier quoted context omitted.
It's not happening to me with Firefox 95.0.1 on Ubuntu 20.04. I'm disabling http3 anyway. Re-enabling it when Mozilla will explain what's going on. 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.
Disable telemetry while you're at it: "Firefox Data Collection and Use" in settings. It seems to have re-enabled itself on some silent update. Sneaky bastards.
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.
Earlier quoted context omitted.
As others said, this happened to all kinds of versions, not just 96.
I was perfectly happy with the one that didn't support this 'feature', and automatic updates are what brought it to my system.
Even if you don't update your browser, the world updates around it
Earlier quoted context omitted.
This isn't a time bomb, it's a symptom of the way modern browsers tend to have centralized I/O which means disk and network traffic goes through a single chokepoint. HTTP3 traffic appears to be able to cause one of Firefox's socket threads to hang, and since everything goes through it, all your network traffic is now dead. Chromium uses a similar model of routing all I/O through specific places, so it's vulnerable to…
It is because: (1) I did not explicitly enable this (2) The telemetry setting seems to have re-enabled itself on some update (3) I don't want any services from Mozilla, I want a browser (4) It worked until it blew up revealing that in fact, I suddenly did have service dependencies And finally, the reason I use FireFox is exactly your last sentence, so to see that they are slipping this in under the radar is a pretty…
Switching to a browser without telemetry and automatic updates won't protect you from this kind of network stack bug.
Earlier quoted context omitted.
I was perfectly happy with the one that didn't support this 'feature', and automatic updates are what brought it to my system.
Yeah, the alternative is running a system with a ton of outdated software, with known bugs and active exploits while casually surfing the "oh-so-cosy-and-entirely-harmless" WWW... 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.
Earlier quoted context omitted.
I was perfectly happy with the one that didn't support this 'feature', and automatic updates are what brought it to my system.
Http3 has existed in ff for a while. What triggered this was some back end service switching to http3, triggering the bug. Even if you don't update your browser, the world updates around it
Seems like I'm disabling automatic updates for the foreseeable future.
Earlier quoted context omitted.
It's not happening to me with Firefox 95.0.1 on Ubuntu 20.04. I'm disabling http3 anyway. Re-enabling it when Mozilla will explain what's going on. 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.
Disable telemetry while you're at it: "Firefox Data Collection and Use" in settings. It seems to have re-enabled itself on some silent update. Sneaky bastards.