The updated BEP-9 does in fact use a multihash under a different key to identify a v2 torrent data. I thought that this was cut out before the final version. The idea of using multihash elsewhere in the protocol was cut, I didn't realize it remained here. So I think the direct mapping is like:. However, it also identifies some other metadata such as piece size, file names, etc. So even with bittorrent v1, it's possible to have two separate magnet links refer to exactly identical content but with different piece sizes for instance.
Great feature adding torrent support! What's the current status no activity on this thread for 4 years? Also does anyone know if there are similar torrent supporting efforts going on in go-ipfs? Skip to content. Star 6k.
New issue. Jump to bottom. Copy link. The commands being: jsipfs torrent add jsipfs torrent cat However, I stumbled upon a question in which we will have to make a decision and I would like to get feedback before going at full speed. I started implementing the IPLD format for a Torrent file , but I'm guessing that most people will want to fetch their torrent through the infoHash of the torrent that they get from a thing like a magnetic URI, the crux is that there is never a file for the info field, as soon as a infoHash query is performed, a Torrent file is retried, rising the question of: Should dag.
Resolve through the Torrent file - This is weird to the IPLD resolver, as it would be resolving an immutable pointer to something that has more fields Resolve only within the info field - This would force us to make the info field a full standalone object that can be transferred independently the solution I'm leaning towards. Member Author. After rethinking this, I remembered why we need ipld-torrent-file and ipld-torrent-info , we need them to enable the resolver to resolve through paths inside these objects i.
When importing a Torrent, two objects need to be created, one for the info and one for the Torrent file itself. This leads to the following steps 1. Implement the IPLD Formats to support torrents ipld-bencode ipld-torrent-file see comment make sure to canonicalize them see comment ipld-torrent-info see comment integrate in ipld-resolver integrate in js-ipfs 2.
Implement a blockstore that uses webtorrent as it's storage driver torrent-pull-blob-store confirm that we can dag. Implement the ipfs-torrent service like ipfs-unixfs-engine module. My understanding may not be entirely correct, but here are the key points as I understand them: v2 torrents use different structures than v1 in the info dictionary and metainfo. What I wrote above is wrong! I apologize for the misinformation. IPLD requirements for js-ipfs BubuAnabelas mentioned this issue Jul 10, Sign up for free to join this conversation on GitHub.
Already have an account? Sign in to comment. Linked pull requests. This limitation is due to how AppImages work and how they containerize their processes. If you are certain that you do not need to use the command-line ipfs commands, then go ahead and install the AppImage.
Open the. AppImage by calling. AppImage from the command-line:. Now that you've got IPFS Desktop installed, you can start sharing files and interacting with other nodes on the network! Visualize your IPFS peers worldwide on a map depicting what nodes you're connected to, where they are, the connections they're using, and more. Click Next : Select the install location for the application.
Ubuntu While these instructions are specific to Ubuntu, they will likely work with most Ubuntu-related Linux distributions. Install with. Double click to install the package with Ubuntu Software, or move into where you downloaded the installer and install from the command-line: sudo dpkg -i. Was this information helpful? Yes No. Edit this page on GitHub or open an issue. Help us improve this site! Suggest new content Request features.
Give general feedback.
0コメント