Magnet link generator
magnetlinkgenerator.com
magnetlinkgenerator.com
I wish IPFS had finished their BitTorrent support so we could use their standard gateway paths instead. The prefix https://ipfs.io/ipfs/f017b1114 should identify a hex-encoded BitTorrent infohash, letting us use a full URL like https://ipfs.io/ipfs/f017b111464d052f755e01d1c947848ad3d2218... through any IPFS gateway, which would resolve the content using a combination of IPFS' own network and BitTorrent with its DHT, but the implementation was never completed.
DHT Sybil attack? Hash ring bloat? Bad peers distributing exclusively irrelevant content?
Wonder if this is a common observation, and if so, what kind of research might elucidate the underlying change.
but magnet URIs are not torrent specific, are they?
I'm fairly sure I'd used them in some other p2p apps years ago.
AFAIR, they are just content identifiers, and could work with any content-addressable system that wanted to support them (IPFS, Gnutella or whatever).
*Edit, I overlooked somethkng.
I've come across magnet links in the past and the torrent client would just find some peers... it was like magic.
I was hoping I could transfer semi-public files (say some music with a friend) without putting them on the public trackers, but my tests with different clients were not conclusive, so those really only make sense for busy, wide-distribution torrents and not one-to-a-few transfers, for which things like magic-wormhole are a better alternative.