[WIP] feat/v0.1.0

[daviddias]

No description provided.

[danimesq]

@daviddias
Label says ready, but title yet is [WIP]

[daviddias]

@DaniellMesquita this is waaay old code :) The ready label is a leftover from Waffle.io (Kanban), where ready was equivalent to backlog. The PR is still not ready.

[danimesq]

Why not prioritizing torrent in IPLD? Which one is more important than that?

[danimesq]

@daviddias

I'm projecting oTorrent app (formly omniTorrent), which would download the same file both from IPFS and from bitorrent, and also seeding both.
You really think torrent isn't the priority for IPLD? And I don't talk about piracy; Ubuntu ISO is a example of how torrents are useful.

[daviddias]

@DaniellMesquita I absolutely believe that Torrents are important for IPLD. It is what IPLD is designed for, to create a way in which any kind of hash linked graphs can interop and through that, create a unifying language to resolve and query that data.

Previous work was:

• Support for Ethereum graphs https://github.com/ipfs/js-ipfs/tree/master/examples/explore-ethereum-blockchain && 🌟 Parity to IPFS ipfs/js-ipfs#763
• Support for git graphs https://github.com/ipfs-shipyard/IGiS
• Unixfs itself is a specialized IPLD Graph.

You can track the progress of adding Torrent support at ipfs/js-ipfs#779 and it seams that the IPLD team intends to ship it soon (i.e. perhaps Q4) ipfs/js-ipfs#1893

[rvagg]

closing for archival