Thread

After several weeks of persistent effort, I'm excited to share Nostr Web Services (NWS). NWS makes your web service reachable without having a publicly accessible IP address or DNS. All you need is an npub and a set of Nostr relays. A wide range of existing services could be run on NWS without requiring any significant changes. NWS achieves this by establishing a TCP connection between client and server which can be used by these applications. Please keep in mind, that the software is in a very early state and not even released yet.
GitHub
GitHub - asmogo/nws: NWS - enable TCP on Nostr
NWS - enable TCP on Nostr . Contribute to asmogo/nws development by creating an account on GitHub.

Replies (18)

🌐👀
User's avatar npub16uq0...xla3
After several weeks of persistent effort, I'm excited to share Nostr Web Services (NWS). NWS makes your web service reachable without having a publicly accessible IP address or DNS. All you need is an npub and a set of Nostr relays. A wide range of existing services could be run on NWS without requiring any significant changes. NWS achieves this by establishing a TCP connection between client and server which can be used by these applications. Please keep in mind, that the software is in a very early state and not even released yet.
GitHub
GitHub - asmogo/nws: NWS - enable TCP on Nostr
NWS - enable TCP on Nostr . Contribute to asmogo/nws development by creating an account on GitHub.
View quoted note →
↩ replying to npub1c80w...h5s7
By having all TCP packets proxied by the entry node, the number of incoming IP addresses for the relay operator is significantly reduced. This simplifies IP blacklisting in case of an attack, as NWS funnels all client requests through the entry nodes. Consequently, the distribution of requests is determined by the total number of entry nodes. If your goal is to DDoS Nostr relays, it's likely more effective to flood them with normal events.
↩ replying to npub120ay...zmfx
Any contribution is welcome! Whether you want to be a contributor, an exit or entry node runner, or just help spread the word. I'm currently working on adding an HTTPS reverse proxy with auto-generated self-signed certificates. This will allow exit node runners to accept encrypted HTTPS connections from public entry nodes without enabling TLS in their backend services at all.
GitHub
Add HTTPS reverse proxy support by asmogo · Pull Request #21 · asmogo/nws
This update includes the implementation of an HTTPS reverse proxy running next to the exit node.