I don't have any specific bug, but 2 transports (rather than just TLS/TCP) with separate crypto handshakes is 2x bug/vuln surface.
Seems like an awful tradeoff when the only point is "make it so 500 ads/trackers/scripts per page don't take forever to load".
-
-
Better solution would be "remove all the ads and trackers, now plain HTTP/1.1 over TLS 1.3 loads instantly".
-
For the end user it will never be "site loads N × faster" anyway. It will be "we can cram in N × as many ads/trackers without losing users".
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.