> Imagine future browsers ( #browstr ) allowing you to enter http://
Brave does that with IPFS. You just go ipfs://
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://
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
Discussion
Interesting. What does the hash represent? How does it bypass the home NAT?
I also think https://holesail.io/ is an interesting project for large traffic.
But for #IoT devices, http-over-nostr would be the best. All kind of Arduino/ESP32 projects can easily connect to websockets, so they could serve simple “websites” for configuration and operation.
It bypasses NAT by using a message bus instead of direct p2p communication. A Nostr relay is that middleman and you probably want to run your own relay, so that needs to be accessible past the NAT (could be hosted on a VPS, or you could spam someone else's relay).
The hash is the hash of the data you're requesting. You have to be running a local IPFS node or Brave will run one for you.