Add BitTorrent info metadata format as 0x7b #35
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also adds BitTorrent's bencoding under serialization formats, but leaves it unassigned for now.
|
@jeremyBanks I just started working on adding Torrents support to js-ipfs, track the progress here ipfs/js-ipfs#779, you are welcome to join this endeavour if you are interested :) Going to complete with this PR with the torrent-file multicodec and add one code for bencode :) |
|
Going to merge this into a branch of the repo, so I can add stuff |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds BitTorrent info metadata format as
0x7b. (Mnemonic:B7for BitTorrent, but transposed so the value remains one byte after unsigned-varint encoding.) Also adds BitTorrent's bencoding under serialization formats, but leaves it unassigned for now.I'm working on some software that includes a web gateway for distributed content. It will initially only serve content from BitTorrent torrents, but I'd like to eventually include interlinked IPFS content, so I intend to move to a path scheme that's as similar as possible (ideally the same/compatible) as that used by IPFS/IPLD/CIDv1.
As a first step I believe I need a multicodec assignment for the BitTorrent format, hence this PR.