So, yes, as you say, Firefox can be fine tuned without going through a myriad of extra fine tunings. With Autoconfig as well as with Group Policies (via Win7’s Registry), with userstyles and userscripts … it’s become Superfirefox (it’s a bird, it’s a plane, it’s a browser? No, it’s Superfirefox!). Personally I have tweaked Firefox, hum… tremendously. Like a motor engine, you have to consider interactions! It’s a question of balance : too much modifications, especially when unaware of a setting’s implications for itself and tied to others harm can do too little can leave a valid one perpetuating things we dislike. I basically agree on the fact that manipulating about:config settings can overdo one’s aim of privacy & security when the basics are in the browser’s options. Now You: did you run into the issue using Allen, interesting topic, initiated by the article and slightly emanipating itself from its genitor :=) Mozilla is working on a fix but it is unclear how long the investigation and bug fixing will take before the issue is resolved. The main workaround for the time being is to change the preference mentioned above to FALSE. Our current plan is to disable HTTP3 to mitigate until we can locate the exact bug in the networking stack. Telemetry was first implicated because it's one of the first services a normal Firefox configuration will connect to, but presumably the bug will trigger with any other connection to such a server.
#Firefox esr slow update#
Our current suspicion is that Google Cloud Load Balancer (or a similar CloudFlare service) that fronts one of our own servers got an update that triggers an existing HTTP3 bug. One commenter suggested that the culprit may be an external service that Mozilla is using: If correct, it would suggest that a Firefox's data collection modules or connection attempts to Telemetry servers are causing the issue.Ī bug report on Bugzilla suggests that the issue may affect other versions of Firefox, including Firefox ESR as well.
0 kommentar(er)
