Replying to Avatar Oren ☂️

Here is another demo of my NIP implementation.

Now using ephemeral events, NIP-44 encryption and NIP-59 gift wraps:

https://github.com/nostr-protocol/nips/pull/1276

I suggest we’ll call it NIP-80 after the default http port.

Imagine future browsers ( #browstr ) allowing you to enter http://.nostr/… and it would simply send the http request and receive the response via nostr events! Just like .onion sites but without the slowness of TOR.

It can also be useful for #iot devices that can serve a simple configuration-website and allow “browsing” them from anywhere in the world. I think TOR is too complicated to run on such devices.

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z WDYT? https://v.nostr.build/VAREX7f6XB8sTPQr.mp4

I think this is an alternative to VPNs instead of Tor. If you want your IP address to be private no matter what, you have to also connect to nostr relays with something like Tor. And if you have a VPN that you trust, you don't need to tunnel traffic over Nostr in addition to that. Or did I miss something perhaps?

Reply to this note

Please Login to reply.

Discussion

Using VPN doesn’t mean you have a static public IP address. It doesn’t mean you can easily configure your computer to become a server in a way that allows others to initiate a connection with it.

I think Tor can give you an onion address, based on your public-key, so it remains yours even if the network changes.

Aha, I see now. It wasn't clear that it's all about hosting. Thanks for clarifying.

Personally, I use ZeroTier or Wireguard for these things, but it could be interesting in some cases still. I think it still doesn't quite replace the privacy of Tor, but could be useful for convenience and/or speed of deployment for certain things.