undefined | Better HN

0 pointsjsheard1y ago0 comments

How does QUIC improve ad deliverability?

0 comments

The entire protocol puts corporate/institutional needs first and foremost to the detriment of human person use cases. HTTP/3 makes all web things require CA TLS and means that if something in the TLS breaks (as it does every couple years with root cert expirations, version obsolecence, acme version obsolecence, etc) then the website is not accessible. Because there's no such thing as HTTP+HTTPS HTTP/3, self-signed HTTPS HTTP/3, or even, as in this case, custom CA TLS HTTP/3. It's designed entirely around corporate/institutional needs and is a terrible protocol for human people. HTTP+HTTPS websites can last decades without admin work. HTTP/3 websites can only last a few years at most.

mardifoufs1y ago

If it was about institutional needs, surely it would make it easier to mitm for middleboxes? The biggest opposition to QUIC came from big corporations and other institutional players

chgs1y ago

Different players. Google and other ad companies are bigger than old companies trying to MITM their users.

persnickety1y ago

This doesn't have much to do with QUIC. If HTTP/3 was based upon another transport protocol, you'd have the exact same problems.

You can use QUIC with custom certs without any trouble.

superkuh1y ago

QUIC isn't just some transport protocol though: it's weird. These restrictions are based in the QUIC libs, not in UDP (which is the QUIC transport protocol).

And while you can use QUIC with custom certs in a technical sense if you do the compile flags and build your own universe, 99.9999% of the people on Earth with their standard QUIC lib implementations (most use the same two) will be unable to connect to it.

1 more reply

intelVISA1y ago

> We explicitly disallow non-publicly-trusted certificates in QUIC to prevent the deployment of QUIC interception software/hardware, as that would harm the evolvability of the QUIC protocol

For Chrome at least..!

josephg1y ago

That has nothing to do with ad deliverability.

j / k navigate · click thread line to collapse

0 comments

superkuh1y ago

mardifoufs1y ago

If it was about institutional needs, surely it would make it easier to mitm for middleboxes? The biggest opposition to QUIC came from big corporations and other institutional players

chgs1y ago

Different players. Google and other ad companies are bigger than old companies trying to MITM their users.

persnickety1y ago

This doesn't have much to do with QUIC. If HTTP/3 was based upon another transport protocol, you'd have the exact same problems.

You can use QUIC with custom certs without any trouble.

superkuh1y ago

QUIC isn't just some transport protocol though: it's weird. These restrictions are based in the QUIC libs, not in UDP (which is the QUIC transport protocol).

1 more reply

intelVISA1y ago

> We explicitly disallow non-publicly-trusted certificates in QUIC to prevent the deployment of QUIC interception software/hardware, as that would harm the evolvability of the QUIC protocol

For Chrome at least..!

josephg1y ago

That has nothing to do with ad deliverability.

j / k navigate · click thread line to collapse