specs

Hi! (Another IPFS dev here :)) IPFS supports today WebRTC, TCP, uTP and WebSockets, thanks to the multi transport approach libp2p[0] offers. In fact, that is how Orbit works, a chat app build completely in JS, using IPFS, on the browser without any plugins. Check: - http://orbit.libp2p.io/ - https://github.com/haadcode/orbit The js-ipfs DHT is underdevelopment, in fact, we have an implementation, but it is not compatible with go-ipfs so we are not rolling it out, yet. To check the latest updates on the project and learn whats next, check our log https://github.com/ipfs/js-ipfs/issues/30#issuecomment-22604... [0] - libp2p is the network stack of IPFS, also a standalone project https://github.com/ipfs/specs/tree/master/libp2p

Thanks for the interest everyone! We think libp2p is one of the most exciting and useful parts of the IPFS project. We've refactored it out of IPFS for the benefit of the general p2p / networking community. We're working on cleaning up interfaces, getting to a good level of completeness and interop between go and js, and then messaging/explanations. Stay tuned for proper a launch later on. But note both go-libp2p and js-libp2p are usable and in use now. :) - Go: https://github.com/ipfs/go-libp2p - js: https://github.com/diasdavid/js-libp2p - specs: https://github.com/ipfs/specs/tree/master/libp2p brb, 8hr flight.

I'd love to see that. I think versioning is possible in IPFS via merkle tree, but I haven't taken the time to understand how it would be implemented. https://github.com/ipfs/specs/tree/master/merkledag

One of the things I am most looking forward to is the abstraction into libp2p[1]. I am wanting to try out my own ideas but I don't want to hassle w/ building my own Kademlia DHT or NAT traversal. 1 - https://github.com/ipfs/specs/tree/master/libp2p

Thanks very much to Christian and John for writing a much needed detailed article :) Some more links for people to check out: ## (upcoming) IPLD "merkleized JSON" format: - improves upon our basic format to make it much more pleasant to build things on top of ipfs. - JSON meets CBOR meets Merkle-linking - mini-spec: https://github.com/ipfs/specs/blob/master/merkledag/ipld.md ## answers to some common questions i've read on this page: - content model / replication: https://github.com/ipfs/faq/issues/47 - how resolution works: https://github.com/ipfs/faq/issues/48#issuecomment-152917088 - how IPNS / mutable linking works: https://github.com/ipfs/faq/issues/16 - this is a very poor answer, sorry, i'll write up a post or paper on it. - for now if interested, see the QConf slides below, specifically slides ~110 to ~130 -- the DNS, IPRS, SFS/Ma