Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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



My browser isn't supposed to have any 'backend services'. Especially not backend services that I did not explicitly opt in to.


It's not a backend service on your browser, it's on whatever webpage you tried to visit.


I really don't get this comment after a whole thread full of good information on this.


No, it's in the browser. Turn off all data collection and the bug disappears.

https://bugzilla.mozilla.org/show_bug.cgi?id=1749908#c10


lower in the linked thread:

> Telemetry has nothing to do with this, it just happens to be one of the first services with H3 load balancer.


You... do understand that that's self-contradictory, right? It's impossible for both parts of that sentence to be true.

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.


I think he means you that you couldn't eliminate the bug by disabling telemetry. It just will be triggered by something else later.


Sure. But the thread is in reply to this post: https://news.ycombinator.com/item?id=29918998

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.


This bug can be triggered without visiting any webpage at all.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: