151–160 of 410 posts
The strange thing it seems to randomly appear/disappear.
Most strangely it happened to trigger the appearance/disappearance of the problem with other people entering the office??
Earlier quoted context omitted.
> However, if you had enabled DoH then you probably do not want to turn it off Or you simply didn't know that Firefox made it the default a while ago. I had it intentionally disabled on one machine but forgot that it's enabled on others, which made troubleshooting even more "interesting"... Why do things work on one machine but not the other?
> Or you simply didn't know that Firefox made it the default a while ago. Oh, interesting! I did not know it is a default now. I can imagine why they would enable it by default, but when Cloudflare (which I assume is the default DoH provider) has a problem at some point everyone is doomed. Really wish they also could make it so the data collection part is opt-in instead of opt-out (which at this point in time appears…
Earlier quoted context omitted.
Read the thread.
Which thread? I have one borked firefox install that I fixed by disabling http3 and one that i checked 30 minutes after the borked one that still works without disabling anything. Same OS same network. I'm wondering why.
This is likely also how it passed QA in the first place. Sometimes it works...
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
Earlier quoted context omitted.
I don't understand the anger about the VPN. I think it's a good idea. Reader mode is useful, especially if you block a lot of CSS and JavaScript by default with uMatrix. I don't know why people use DOH anyway. It bypasses your hosts file, so you can't block things as easily.
>It bypasses your hosts file It doesn't bypass my hosts file... I have a couple of locally hosted websites that I have rules in /etc/hosts for, and Firefox resolves them correctly even with DOH enabled.
"HTTP/3 uses QUIC, a transport layer network protocol which uses user space congestion control over the User Datagram Protocol (UDP)."
Ok. Is it still a thing with internet core routers that in case of congestion issues they drop datagram packets because they're not guaranteed to be delivered anyway?
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]
I love Firefox. It's depressing to see the hate they're getting in the comments.