First iteration of interface-ipfs-core

[hackergrrl]

Here are some thoughts on the herculean task of building this out. For each section of the API (objects, blocks, etc) we

1. write up a draft api for them as a PR in this repo
2. get approval on that PR from the core js-ipfs devs
3. write PRs on js-ipfs and js-ipfs-api to match said api
4. write tests here on interface-ipfs-core for that api
5. run both js-ipfs and js-ipfs-api against the interface-ipfs-core tests from (4)

We'll need this done for the whole core api:

high priority:

• objects
  • draft api
  • api approval
  • js-ipfs support
  • js-ipfs-api support
  • interface-ipfs-core tests
  • tests passing against js-ipfs and js-ipfs-api
• blocks
  • draft api
  • api approval
  • js-ipfs support
  • js-ipfs-api support
  • interface-ipfs-core tests
  • tests passing against js-ipfs and js-ipfs-api
• add
  • draft api
  • api approval
  • js-ipfs support
    • refactor out filesystem pieces
  • js-ipfs-api support
  • interface-ipfs-core tests
  • tests passing against js-ipfs and js-ipfs-api
• cat
  • draft api
  • api approval
  • js-ipfs support
  • js-ipfs-api support
  • interface-ipfs-core tests
  • tests passing against js-ipfs and js-ipfs-api
• get
  • draft api
  • api approval
  • js-ipfs support
  • js-ipfs-api support
  • interface-ipfs-core tests
  • tests passing against js-ipfs and js-ipfs-api

lower priority:

• version
• id
• refs
• pin
• log

[daviddias]

Thank you, I love things that look like Roadmaps! :)

In terms of process, let's go more for:

• 1. Write up the API spec in a PR
  • 1.1 Write up the tests for that API
  • 1.2 Write up PR for js-ipfs and js-ipfs-api that apply the tests and necessary changes
  • 1.3 Tweak the API spec as needed (feeding back what is learned from writting and applying the tests)
• 2. Once happy, merge them all

[daviddias]

Remaining (up for grabs :)):

• files (mfs) Files, the Mutable File System API #38
• name name API #37
• dht DHT API #36

[daviddias]

@victorbjelkholm is handling files and DHT, name will be ms6. Closing this issue as clean up, tracking happens on the PR referenced in #18 (comment)

[daviddias]

@victorbjelkholm is handling files and DHT, name will be ms6. Closing this issue as clean up, tracking happens on the PR referenced in #18 (comment)

[Stebalien]

@diasdavid I think the refs API is still missing.

[ntninja]

Any information on the refs API? Is there any difference between object.links(multihash) & refs(multihash)?