Replying to Avatar MichaelJ

WebSocket is firmly established as the communication protocol for Nostr, at this point, and to break from that entirely would be to break compatibility with the larger network.

That said, I don't see a problem with relays offering different transport options for the same events. If every relay offers WebSocket, some may additionally offer protocol extensions to alternately use WebTransport or HTTP, for instance.

A client should be able to connect to any relay using WebSocket, but specialized relays offering additional communication protocol options may have a place.
Avatar
発火大根 hakkadaikon🎤 1y ago

Thank you!

I will try to verify whether I can successfully implement the RUDP or WebTransport protocol stack as an extension protocol in the WebSocket server.

I will also check the nips issue (1671).

Reply to this note

Please Login to reply.

Discussion

Avatar
MichaelJ 1y ago

I don't think it should be an extension _to_ WebSocket, just that relays need some way of advertising "I can use RUDP!" or "I can use WebTransport!" so clients know which relays they can try to connect to using those protocols.

Definitely look into the NIP-91 proposal, like you mentioned; it may be a good fit for this.