Glad to see that Nostr people discover IPFS, which we use in web3 for years 😀

nostr:nevent1qvzqqqqqqypzqd4me2qsu2h2lzfep0lr2k3x3k336qc2f8muguj0n5d2vn504l8uqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqss4389yr48244w826u9hzvvrl9u0demmyhme6x34cc5fr409j8cqkmf2k0

Reply to this note

Please Login to reply.

Discussion

Many things like that here. Look here, where nostr belatedly discovers ngrok.

In short, this NWS thing was where a so-called “entry node" captures some web traffic, wraps it into an encrypted Nostr event which is then sent to a relay that holds it until an “exit node” fetches it, decrypts the event, sends it to the local web server, and then sends the response back through the relay the same way.

It, err, didn't take off.

So many things like this.

nostr:nevent1qvzqqqqqqypzq5xeflpdskqvdq4swxj59793uvdzqzc9pzatjk3nhmcg2h0js8trqqs9xzrlasmnzyklfsl968cmr53ggua4tagpyhwkh5mypaq3etfwtng5hsejz

Oh yeah... The only correct solution for IPFS<->Nostr is to implement the IPFS interface directly into Nostr clients (new NIP), so i can set up a connection to my own IPFS node, or choose preferred gateways. Images could then be referenced only by CID.

Hell yeah! Arweave is also another solution that is aligned with foreverness of BTC