IPFS & IPLD would be great too..
https://github.com/nostr-protocol/nips/pull/345 is pretty ingenious and simple, and could be a good thing, even though I agree with all the criticisms it has received too.
But personally I don't understand why we can't just use torrents. BitTorrent already supports "webseeds", which are servers that literally serve the file, and the same file can be served from many of these servers. BitTorrent is a very simple protocol too, with many libraries and implementations in many different languages. There is no reason to reinvent things.
Or maybe there is. What is the reason? What can this (or other similar proposals) do that BitTorrent directly can't?
Discussion
No way.
We're testing js-ipfs client on browser to index everything from Nostr & eth sides as linked data.
**still missing some full ipfs node features on browser & really hard to pubsub.. That's why we're using Nostr instead of ipfs-pubsub. ;) but for basic distributed storage & linked data it's similar tech stack as web+torrent with magnet link like content identifier/hash.
```
const _ipfs = await Ipfs.create({
config: {
Addresses: {
Swarm: [
// This is a public webrtc-star server, add more
"/dns4/wrtc-star2.sjc.dwebops.pub/tcp/443/wss/p2p-webrtc-star",
"/ip4/127.0.0.1/tcp/13579/wss/p2p-webrtc-star" // run your own webrtc
]
},
Bootstrap: ["/dnsaddr/bootstrap.libp2p.io/p2p/QmNnooDu7bfjPFoTZYxMNLWUQJyrVwtbZg5gBMjTezGAJN",
// add more bootnodes,
]
}
});
let test = {
".well-known": {
"nostr.json": {
"hello" : "world"
}
}
};
let ipld = await _ipfs.dag.put(test);
console.log("ipld://" + ipld.toString());
```