The main goal of NWS is to make services resilient and accessible for everyone.

Nostr is a fantastic tool to help us achieve this. There are situations where we need to rely entirely on Nostr for TCP transport, such as when the entry node isn't publicly available as a service. However, for our primary use case—having a publicly accessible entry node—we don't need to use Nostr for transport.

That's why I've just added a new connect reverse mode that uses Nostr for "service discovery". Once the service is discovered on the relay, a direct TCP connection is established between the entry and exit nodes.

By using direct connections, we can ensure more reliable service availability and faster connectivity.

https://github.com/asmogo/nws

Reply to this note

Please Login to reply.

Discussion

Amazing!

Cool cool

Have no idea what this means but sounds impressive!

*DCC nostalgia intensifies*

nostr:note15eppg84dtdslyvpujr9puyaek9a5k5xdx9vqhypygsl6dfdxlesqlq3zjc

i predict that in the coming year we will see nostr relays with sockets to tor connections that you can pay to send traffic through (most likely included in the subscription level) - and other things too... it's a natural progression IMO

the simple coordination layer will make a lot of things easier to implement

Saw you are working on domain parsing for `.nostr` addresses too - now I can't help but spend a few more hours today tinkering with this.