> However, often HTML/HTTP(S) is just the wrong protocol for many things Indeed! First we lost all of the IP protocols except TCP and UDP, thanks to aggressiv

> However, often HTML/HTTP(S) is just the wrong protocol for many things Indeed! First we lost all of the IP protocols except TCP and UDP, thanks to aggressive firewalls. NAT managed to kill any hope of end-user hosts acting as true servers, so we ended up with a client-server internet. Another round of aggressive firewalling killed off pretty much everything except for 53/udp, 80/tcp, and 443/tcp. Middleboxes playing with unencrypted DNS and HTTP then broke 53/udp (good luck introducing new RR types or extending the protocol now!) and 80/tcp. Now we're left with HTTPS on 443/tcp as our only remaining protocol that actually works reliably for end users in the real world internet. [Not to mention the fact that iOS and Android 8+ both prevent applications from holding long-lived server connections. Want real-time notifications? No choice but to go through the vendor's push notification service.]