RT @programmingart@twitter.com
Part 2/3 of my series "HTTP/3 from A to Z" is now online. In it, I discuss #HTTP3 and #QUIC's performance features in technical detail and nuance.
Learn why the new protocols certainly improve things but often don't entirely solve problems @smashingmag@twitter.com: https://www.smashingmagazine.com/2021/08/http3-performance-improvements-part2/
🐦🔗: https://twitter.com/programmingart/status/1429716006717493248
#QUIC also means no intermediate proxy. Nobody ever consider what this means in term of user #privacy vs large cdn and cloud providers?
We could have faster web contents (beware, not faster web apps or streamings, just web contents) with something as simple as cryptographically signed tar.gz containing website chunks (such as css+images+html):
- fast (RTT becomes totally irrelevant)
- fully cacheable
- authenticated (no MitM)
It would not be encrypted (and thus not good to send your credit card or transfer sensible data or contents) BUT it would make centrally spying on all people way more difficult.
Instead Google invented QUIC.
No way to cache contents and to ensure their authenticity without connecting to the TLS servers.
Well done, engineers, well done!
And yes, IETF QUIC is different from Google QUIC: it doesn't serve only the needs of #google but those of #Facebook, and #Cloudflare and friends.
You wrote that this "is a real concern", but I don't think you stressed enough what a huge issue geopolitical this is: it should be enough to ban QUIC traffic outside the #USA.
