31–40 of 72 posts
The title is misleading, Google has not broken anything, Dutch providers have. I hope Google will do nothing, and the providers will be pressured into fixing their shitty hardware.
The title is misleading, Google has not broken anything, Dutch providers have. I hope Google will do nothing, and the providers will be pressured into fixing their shitty hardware.
Funnily I switched to Microsoft Edge for a short while, but have once again realized why its unusable. After about 1-2 minutes using it, the entire browser became unresponsive for about 60 seconds. Afterwards I couldnt press sign-in on YouTube because an invisible IFrame from the OneNote Web Clipper Extension was overlaying it. Nobody seems to be testing those either :)
same here in Germany on windows this morning.. also had to disable QUIC. Funnily I switched to Microsoft Edge for a short while, but have once again realized why its unusable. After about 1-2 minutes using it, the entire browser became unresponsive for about 60 seconds. Afterwards I couldnt press sign-in on YouTube because an invisible IFrame from the OneNote Web Clipper Extension was overlaying it. Nobody seems to b…
Anybody seen anything like that? Is it possible that a corrupted packet could appear as a self-signed certificate? Did some MITM screw up?
The title is misleading, Google has not broken anything, Dutch providers have. I hope Google will do nothing, and the providers will be pressured into fixing their shitty hardware.
There's no hardware cause, it appears to be a minor chrome update combined with a QUIC server-side update (unconfirmed) that caused issues. As soon as Chrome auto-updates to the next minor release, things appear better (but not fully fixed).
It's entirely in the browser Google server-side, ISPs have nothing to do with this.
This looks like an implementation error, either client or server-side.