jbz
boosted
dch :flantifa: :flan_hacker:
boosted
Spent way too long getting HTTP/3 working on FreeBSD with nginx, so I wrote it all up.
The highlights: stock OpenSSL silently breaks QUIC at the HTTP/3 framing layer (the TLS handshake succeeds, so openssl s_client lies to you). eBPF worker routing doesn't exist on FreeBSD. And if nginx is in a jail with IPv4 NAT, a pass rule for UDP 443 is useless without a matching rdr.
New post: https://blog.hofstede.it/http3-on-freebsd-getting-quic-working-with-nginx-in-a-bastille-jail/
Spent way too long getting HTTP/3 working on FreeBSD with nginx, so I wrote it all up.
The highlights: stock OpenSSL silently breaks QUIC at the HTTP/3 framing layer (the TLS handshake succeeds, so openssl s_client lies to you). eBPF worker routing doesn't exist on FreeBSD. And if nginx is in a jail with IPv4 NAT, a pass rule for UDP 443 is useless without a matching rdr.
New post: https://blog.hofstede.it/http3-on-freebsd-getting-quic-working-with-nginx-in-a-bastille-jail/
Chewie
boosted
@daniel@gultsch.social
#QUIC (and #HTTP3) exists to serve the interests and needs of #Google.
In particular 0-RTT is basically a low-level cookie that allows deterministic user tracking below and before #http: if it will ever spread, disabling or deleting cookies, even out-lawing them, won't be a issue for #SurveillanceCapitalism.
So these days what happens at #IETF is much more lobbying than engineering. Overpaid engineers lobby against the users to further cement the power of their corporations.
I wouldn't call these as "improvements".
These days, sadly, IETF is the place where the fundamental fabric of the internet is constantly being ^^enshittified**.
@lorenzo@snac.bobadin.icu
#QUIC (and #HTTP3) exists to serve the interests and needs of #Google.
In particular 0-RTT is basically a low-level cookie that allows deterministic user tracking below and before #http: if it will ever spread, disabling or deleting cookies, even out-lawing them, won't be a issue for #SurveillanceCapitalism.
So these days what happens at #IETF is much more lobbying than engineering. Overpaid engineers lobby against the users to further cement the power of their corporations.
I wouldn't call these as "improvements".
These days, sadly, IETF is the place where the fundamental fabric of the internet is constantly being ^^enshittified**.
@lorenzo@snac.bobadin.icu
@daniel@gultsch.social
#QUIC (and #HTTP3) exists to serve the interests and needs of #Google.
In particular 0-RTT is basically a low-level cookie that allows deterministic user tracking below and before #http: if it will ever spread, disabling or deleting cookies, even out-lawing them, won't be a issue for #SurveillanceCapitalism.
So these days what happens at #IETF is much more lobbying than engineering. Overpaid engineers lobby against the users to further cement the power of their corporations.
I wouldn't call these as "improvements".
These days, sadly, IETF is the place where the fundamental fabric of the internet is constantly being ^^enshittified**.
@lorenzo@snac.bobadin.icu
#QUIC (and #HTTP3) exists to serve the interests and needs of #Google.
In particular 0-RTT is basically a low-level cookie that allows deterministic user tracking below and before #http: if it will ever spread, disabling or deleting cookies, even out-lawing them, won't be a issue for #SurveillanceCapitalism.
So these days what happens at #IETF is much more lobbying than engineering. Overpaid engineers lobby against the users to further cement the power of their corporations.
I wouldn't call these as "improvements".
These days, sadly, IETF is the place where the fundamental fabric of the internet is constantly being ^^enshittified**.
@lorenzo@snac.bobadin.icu
I started going to IETF meetings. Those events take place 3 times a year, with ~1000 people attending in person and another ~1000 remotely. A good chunk of those are paid to be there and some are employed by big companies like Apple and Google. This is the place where the fundamental fabric of the internet is constantly being improved. TLS 1.3, HTTP/3, MLS to name a few.
With this in mind I have no fucking clue what Moxie was on about when he said interoperable protocols are stuck in the 1990s.
@daniel@gultsch.social
#QUIC (and #HTTP3) exists to serve the interests and needs of #Google.
In particular 0-RTT is basically a low-level cookie that allows deterministic user tracking below and before #http: if it will ever spread, disabling or deleting cookies, even out-lawing them, won't be a issue for #SurveillanceCapitalism.
So these days what happens at #IETF is much more lobbying than engineering. Overpaid engineers lobby against the users to further cement the power of their corporations.
I wouldn't call these as "improvements".
These days, sadly, IETF is the place where the fundamental fabric of the internet is constantly being ^^enshittified**.
@lorenzo@snac.bobadin.icu
#QUIC (and #HTTP3) exists to serve the interests and needs of #Google.
In particular 0-RTT is basically a low-level cookie that allows deterministic user tracking below and before #http: if it will ever spread, disabling or deleting cookies, even out-lawing them, won't be a issue for #SurveillanceCapitalism.
So these days what happens at #IETF is much more lobbying than engineering. Overpaid engineers lobby against the users to further cement the power of their corporations.
I wouldn't call these as "improvements".
These days, sadly, IETF is the place where the fundamental fabric of the internet is constantly being ^^enshittified**.
@lorenzo@snac.bobadin.icu