🌟 Do you want to implement IPFS in a new language, get started here!

[flyingzumwalt]

If someone wants to create an IPFS implementation in a new language, the best starting point is to create the supporting libp2p and multiformats modules. Those modules are useful beyond IPFS and you absolutely need them in order to have a working IPFS implementation in your language.

[daviddias]

Thank you for capturing this @flyingzumwalt. Here is an up to date list, of all of this supporting modules with their respective implementations in go and JS + specs.

Supporting Modules

• multiformats
  • multihash spec
    • multihash impl JS go
    • multihashing (utility) JS go
  • multiaddr spec JS go
  • multicodec spec
  • multicodec-packed spec JS go
  • multistream-select spec JS go
• libp2p
  • libp2p-crypto JS go
  • peer-id JS go
  • peer-info JS go
  • peer-book JS go
• ipfs
  • ipfs-repo spec JS

[flyingzumwalt]

@RichardLitt where does this info belong? It's relevant to ipfs, libp2p and multiformats.

[RichardLitt]

This should probably be here, in community, I think. The first step towards building IPFS in a different language is through getting community support. We can add this stuff as a guide: "How to implement IPFS in your favorite language".

Let's pull this into a document here; sound good?

[theobat]

Is there a per-language (excluding JS, Go and python) state of the art channel/discussion already somewhere? I am wondering because I know there are several modules already implemented in several languages but I can't find an exact or concise summary of each. Especially for the languages without a general ipfs directory yet (like java-ipfs or rust-ipfs etc).

Moreover -just out of curiosity- is there a priority order for protocol Labs in terms of what the next language should be ? (or is this left to the community ?)

[kevina]

I would be willing to write (or help write) something in C++ if there is interest.

[flyingzumwalt]

@theobat that's a great question! @RichardLitt it looks like we meant to set up a reference page with this info but both forgot. I like @theobat's question about finding existing efforts to implement IPFS in a given language. Are we tracking that anywhere? @whyrusleeping @diasdavid do you know? Does anyone have ideas how we we should track this?

[kenCode-de]

On Wed, Oct 26th 2016 (next week) we begin the c-ipfs implementation.
https://github.com/kenCode-de/c-ipfs

There will be 5 of us working on it to begin with. If you will be contributing, you can also join our skype group if you'd like, so just email me your skype name and I will add you. Please and Thanx! :)

[dyba]

@kenCode-de What time zone are you in and what time will the meeting start on Wednesday? Your Github page says you're located in Germany, is that correct?

[kenCode-de]

yep, i live in munich but the skype meeting is at 0930 GMT on wednesday. we are beginning the c-ipfs implementation. we have at least 5 guys who have committed so far and i hope we can round up a few more...

[dyba]

@kenCode-de I work during that time. Can you record the Skype conversation? I think recording only the audio should be sufficient so that sharing it isn't an issue.

[RichardLitt]

@theobat that's a great question! @RichardLitt it looks like we meant to set up a reference page with this info but both forgot. I like @theobat's question about finding existing efforts to implement IPFS in a given language. Are we tracking that anywhere? @whyrusleeping @diasdavid do you know? Does anyone have ideas how we we should track this?

Let's do it then. :)

I think we are only tracking different efforts on ipfs/ipfs, both in the README here and in the issues, where people can check issues (cf https://github.com/ipfs/ipfs/issues/164).