Subnostr

Hi, All.

I recently developed a WebSocket server.

I plan to embed this WebSocket server into a future Nostr relay that I will develop, with enhanced documentation, comments, and testing.

https://github.com/Hakkadaikon/websocket/tree/main

By the way, there's something I've been thinking about lately.

Nostr runs on top of WebSockets, And WebSockets run on top of TCP/IP.

In the case of TCP/IP, data cannot be received in bulk using a system call, so we believe there is a problem in that it is difficult to improve performance beyond a certain level.

I believe that if Nostr were run over a UDP protocol such as WebTransport, RUDP, etc..., Nostr relay could operate even faster.

For a plain Nostr relay delivering text events, probably won't need to go this far.

However, I think this Nostr relay can be useful for delivering volatile, streaming, real-time data.

In the future, I plan to create a PoC that runs Nostr on the UDP protocol.

What do you think?

Comments, positive or negative, are welcome.

#nostr #grownostr

ChipTuner 1y ago

In terms of nostr, I think I would consider transport optimizations as a microoptimization. Many high speed data transfer protocols are run via TCP and don't consdier it to be enough of an issue to build a UDP enabled application layer.

However the other foundational principal for nostr is that it's primary focus is simplicity and availability with existing technology. Most applications/frameworks can more easily have access to websockets effectively giving them access to the transport with the help of http.

However I'm with nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn relays that have the option to support or upgrade connections for clients that can receive them is a great direction to head in, but were still early, nostr needs working and tested software not optimizations at this stage.

Reply to this note

Please Login to reply.

Discussion

No replies yet.