- lets us opt of automatic meddling from Mozillas side
- fixes a single small thing every month
I want to pay for it.
71–80 of 410 posts
- lets us opt of automatic meddling from Mozillas side
- fixes a single small thing every month
I want to pay for it.
Update: using Google's (the horror) DoH, and I didn't notice problems. Might just be CF having a bad H3 deployment, but I want to know what bug it triggered on FF.
Update 2: To clarify, CF did indeed hang FF, but also Google, which is know for at least bothering to monitor complaints (and dns.google is still H2). Trying to disable telemetry now.
Update 3: incoming.telemetry.mozilla.org is still H2. Can someone give me the other domains of MozTelemetry? Browser still working as of the moment.
Update 4: Telemetry was indeed H3'd: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c17, me angery right now.
It is time for Mozilla to stop messing around. They are losing user trust extremely fast. A silent FireFox update that cripples the browser? No active update was done since yesterday and this morning: a broken browser. Please stop non-browser development and let me pay a monthly fee for a decent browser! I don’t want a VPN service, bookmark readers or other crap. I want Mozilla to defend the open web and create an op…
I don't know why people use DOH anyway. It bypasses your hosts file, so you can't block things as easily.
https://twitter.com/vanilla_chief/status/1481546294489489409
€: It seems telemetry does no longer triggers the bug as they've changed something on the server side? So this probably won't help anymore.
What's driving me crazy about Firefox is that every time they release a new version, whatever version I am running on my machine stops working-- it refuses to load any new page or to refresh any existing page. So I have to open Safari and download and install the latest release. Which means I can never count on Firefox working. Frustrating. osx, if that helps anyone suggest a fix.
What's driving me crazy about Firefox is that every time they release a new version, whatever version I am running on my machine stops working-- it refuses to load any new page or to refresh any existing page. So I have to open Safari and download and install the latest release. Which means I can never count on Firefox working. Frustrating. osx, if that helps anyone suggest a fix.
But I'm starting to believe that the browser wars have been conclusively lost and it's time to throw in the towel. Losing a whole morning on this trick is really pissing me off, I'm in the middle of a bunch of stuff and if not for this HN thread I'd be unable to continue to work. Very, very annoying. Browsers are mission critical, you don't just fuck around with the networking settings on a timed change.
What worked for me was disabling HTTP3 support with the 'network.http.http3.enabled' key in about:config and then restarting Firefox. Seems like it's stuck in the 'SocketThread', repeatedly doing this: 2022-01-13 08:20:53.075936 UTC - [Parent 4106991: Socket Thread]: V/nsHttp Http3Stream::OnReadSegment count=333 state=4 [this=7f6e295623a0]
Oh man and I thought it was only me. I couldn't even refresh Firefox from the UI and had to start it in safe-mode to reset everything. That fixed it but holy moly
I really hope the auto-update component doesn't have the same issue, otherwise Firefox is essentially dead on millions of computers owned by non-techies.
Exactly what I was thinking. I hope they thought about this case and made the updater use a different stack...
Can't access any website or making any connection without disable `network.http.http3.enabled` and restart.
This impact is huge for million of firefox users!