jb55 on Nostr: there’s no reason you couldn’t have a hybrid torrent/blossom client: create a v2 ...
there’s no reason you couldn’t have a hybrid torrent/blossom client:
create a v2 torrent with a bunch of file hashes stored on blossom. The torrent could even have blossom nodes embedded in it the way it embeds trackers.
Then a client could lookup these file hashes in the p2p network or on the blossom nodes. If all the blossom nodes go down then it can fallback to p2p.
create a v2 torrent with a bunch of file hashes stored on blossom. The torrent could even have blossom nodes embedded in it the way it embeds trackers.
Then a client could lookup these file hashes in the p2p network or on the blossom nodes. If all the blossom nodes go down then it can fallback to p2p.
quoting note128s…9v9qlooks like #bittorrent dev has kinda stalled recently. many torrent devs are working on shitcoin projects now (chia, tron). Not many clients have v2 support. Maybe we need more bittorrent v2 implementoors. I am itching on hacking support for this in notedeck 🤔
bittorrent is not all about piracy. could be an interesting way to share files on nostr, as an alternative or combined approach with blossom.
bittorrent v2[1] is interesting because of its merkle hash trees: the same file can be replicated across torrent swarms.
So if you share a directory with multiple files in one torrent, and that files exists in other torrents, you can share the same seeders for those files. Maybe you could even use #blossom nodes as seeders if they have a merkle root hash that you need?
Lots of cool possibilities here 🤔
[1] https://blog.libtorrent.org/2020/09/bittorrent-v2/