Open problem
The certificate barrier
open
The two most used web transports, HTTPS and WebSocket, require a certificate from a certificate authority. A certificate requires a domain, renewal automation, and an operator willing to maintain both.
“Dialable from a browser” therefore currently means “operates a domain with a CA-issued certificate.” That is an operational posture, not a technical capability. It determines who can serve browsers, and it favors professional operators over hobbyist nodes.
CA-free transports are the candidate direction. WebTransport with serverCertificateHashes needs no CA, and libp2p’s WebRTC-direct achieves the same over WebRTC. See connectivity for their constraints.