Thread - Nostr Hypermedia

Mike Dilger ☑️ mike@mikedilger.com 7 months ago

Iroh is over QUIC, which has great features but it is UDP, meaning you can't use Tor. So it doesn't provide both privacy and p2p. Also web-based clients probably can't do QUIC and even if they can, they are not going to accept the TLS "raw public key". No single transport can make everybody happy: websockets: the only transport that works in browsers. Also works with Tor. But you rely on DNS and CAs and it is the lowest performance choice. tcp: wouldn't have to rely on DNS and CAs, Tor is supported, and performance is in the middle. But cannot support browser based clients. quic: wouldn't have to rely on DNS and CAs, and it has the best performance by a long shot. But you can't use Tor or browser-based clients.

↑ Parent

Replies (2)

Repeatedly nuked profile 7 months ago

Doesn't WebTransport get you CA-less QUIC in browser? Via the server cert hashes thing? Like as long as it matches one of the hashes *you* provide then you're good?

2 replies ↓

Daniel Wigton dwigton@getalby.com 7 months ago

Not allowing browser based clients is a feature 😈 I kid.. sort of. There isn't any reason browsers can't be extended to support quic etc. I think you kinda want to be connection type agnostic. There are connections you'd prefer (quic) or connections you'd settle for (tcp, Bluetooth) The nice thing is that you don't have to develop them all at once. You just pick the easiest to implement and make an algorithm that "chooses" ```return ConnectionType::quic``` then add types after it works at all and as demand develops.

1 replies ↓