State of IPFS

[ReisenB]

It's not done. But, enough of it may be done to get something off the ground. Currently, it would appear the final remaining components needed for js-ipfs to be properly usable in the browser are the relay code and the dht. As of writing, js-ipfs is at 0.23, and one of those two required features WILL ship in 0.24, while the other MAY be delayed to 0.25.

go-ipfs currently has all the components in place already, but it can't be used in the browser without prior installation.

It should be noted that both go-ipfs and js-ipfs have pretty much equivalent APIs, and I have verified that js-ipfs and js-ipfs-api hooks are basically identical (with some disparity based on unimplemented hooks on each side). So, code written for node can be used with either backend without incident. I have not yet checked whether the situation is the same from the Go POV.

[ReisenB]

0.24 dropped, and supposedly there's a partially functional DHT in there but unfortunately it's not done yet. 0.25 it is.

[ReisenB]

0.26 and still no relay or cross-compatible DHT.

To be specific we're waiting on ipfs/js-ipfs#830 and ipfs/js-ipfs#856 getting done. I'm not going to try and predict when they finally get done this time, never works. It's definitely looking better than it was 3 months ago though.

[daviddias]

Subscribing to this issue. @ReisenB let me know if you have questions :) Working as fast as possible to get all the pieces in place!