fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-12-24 17:52:11 +00:00
Code Issues Projects Releases Wiki Activity

New note: in defense of QUIC

Browse source
This commit is contained in:
Rohan Kumar 2022-10-24 21:58:32 -07:00
parent df61b3f3f8
commit bc34916c10
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
content/notes/in-defense-of-quic.md Normal file
View file

@ -0,0 +1,13 @@
---
title: "In defense of QUIC"
date: 2022-10-24T21:58:32-07:00
replyURI: "https://deadinsi.de/@cybertailor/109226380700850932"
replyTitle: "useless standard, couldn’t care less"
replyType: "SocialMediaPosting"
replyAuthor: "jan Anja"
replyAuthorURI: "https://sysrq.in/en/"
---
I face lossy connections, and QUIC noticeably improves latency: connections establish in just one or zero round-trips and loss doesn't cause as much re-transmission. Add forward error correction and QUIC makes lossy connections *much* less painful. This isn't just for "adtech websites streaming video": the biggest beneficiaries are networks like Matrix and XMPP.
There are much bigger things to worry about regarding Google's control of standards: advertising identifiers, high-entropy client hints, etc. all rolling out *before* the Privacy Budget is what I'd rather focus on. I think there's a lot of misplaced negative attention on a transport protocol that gives tangible benefits to people with worse connections.