3 ms·
I would've accepted that train of thought if it wasn't for their earlier posts about how HTTP/3 is making their lives more difficult. I don't know what's happen
by jeroenhd 4y ago
I would've accepted that train of thought if it wasn't for their earlier posts about how HTTP/3 is making their lives more difficult. I don't know what's happening to their firewall, but these people seem to run into HTTP/3 problems all the time. There's a difference between "I'm not switching to electric cars yet" and "I'm not switching to electric cars yet after I've burned down my house three times installing electric chargers".
Their network is somehow horribly broken and that leads them to pain a picture as if the protocol is somehow inherently stable or problematic to turn on. They're projecting their own misconfiguration onto the wider internet as a whole, and this is exactly the kind of behaviour that has led to the protocol ossification we see today.
- jefftk 4y agoIs this the earlier post you were thinking of? https://utcc.utoronto.ca/~cks/space/blog/sysadmin/HTTP3AndOurFirewalls https://utcc.utoronto.ca/~cks/space/blog/sysadmin/HTTP3AndOu... I think that post is much less reasonable, but it's also almost 2 years old and they may not be doing that kind of blocking anymore?
- jeroenhd 4y agoI think they must've stopped blocking HTTP/3 at some point because the author has had other HTTP/3 related issues they posted about since. However, as of this post: https://utcc.utoronto.ca/~cks/space/blog/sysadmin/WireGuardForFirewallBypass https://utcc.utoronto.ca/~cks/space/blog/sysadmin/WireGuardF... I think it's still safe to consider their network setup hasn't changed much.