Recent submissions

Comment · 2 years ago
> HTTP/3 was designed for unstable connections, such as cellphone and satellite networks.

Satellite networks are not a good example. Regular HTTP/1.1, paired with a PEP, outperforms HTTP/3 by an order of magnitude.

Comment · 2 years ago
The issue you linked to is an excellent example of why everyone and their dog is becoming a CNA these days. It's the only way to keep CVE spam at bay. The system has been broken by the gamification of CVEs and is in desperate need of reform.
Comment · 2 years ago
Isn't the QUIC transport the default since v0.6.0? Compared to TCP, it's much better suited for satellite communications.
Comment · 3 years ago
Anything that involves high latency and/or packet loss. And in general: testing servers.

The question is also a bit odd, to be honest. There's no need to look for a beneficial use case to add support for the next iteration of the HTTP protocol.

Comment · 3 years ago
Comment · 3 years ago
Comment · 3 years ago
Comment · 4 years ago
Comment · 4 years ago
Comment · 4 years ago
Comment · 6 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton