daviddias

Yes, we use it today! libp2p is the P2P Networking Stack of IPFS that we refactored into its own project so that others could take advantage and be part of its ecosystem as well.

It is what gives IPFS and other projects the P2P connectivity, support for multiple platforms (including Browsers) and more! There are 3 implementations interoperable today at different stages of completion (Go, JS for Node.js & Browser and Rust). Full overview here https://www.youtube.com/watch?v=CRe_oDtfRLw

Also, Chris Pacia recently delivered an amazing talk at QCON about libp2p https://www.infoq.com/presentations/blockchain-libp2p, I totally recommend checking it out.

You can find more talks of examples and use cases at https://libp2p.io/media.

Give it a spin and post feedback on github.com/libp2p. We are also on #libp2p on freenode, come say hi!

Congratz on developing Gun! I've looked at it before and I was super impressed! The decision to use Y.js instead was done due to its modularity. We added IPFS support by simply publishing a connector https://github.com/ipfs-shipyard/y-ipfs-connector which Kevin Jahns later added to the list of connectors - https://github.com/y-js/yjs/issues/77

We have linked Y.js from the page header, if you click the word CRDT it takes you to Y.js directly. Nevertheless, I agree that we need to make it more obvious How we appreciate all the work that Kevin has put into Y.js :) Do not worry, PeerPad nor our CRDT usage is finished, there will be a lot more! (In fact, PeerPad was built with little less than 4 weeks of actual dev time, there is so much more we can do).

I'm following up by email, I'm interested in testing Gun as well. Meanwhile, join the CRDT discussion on the Research CRDT (https://github.com/ipfs/research-crdt) Repo, would love to have your input there.

Cheers!

Excited that you found PeerPad so fast. We've released its alfa just a week ago at Mozfest (https://github.com/MozillaFoundation/mozfest-program-2017/is...).

I see that there are some questions about PeerPad's architecture. If you would like to know how it works, I invite you to glance through the Architecture.md at https://github.com/ipfs-shipyard/peerpad/blob/master/docs/AR... If there are things that are not clear to you please open an issue so that we can make it better.

Also, you can expect to see soon a video tutorial of how to build a p2p flipchart using the same underlying kv store that PeerPad uses, y.js + IPFS. If you can't wait you can always take a look at https://github.com/ipfs-shipyard/p2p-flipchart and see how it works :)

We will continue working on PeerPad and add the remaining features necessary to make it usable for meeting notes, publishing and more. You can track the development and also help us built it through the Github Repo https://github.com/ipfs-shipyard/peerpad

Thank you \o/

https://github.com/ipfs/?utf8=%E2%9C%93&query=ipfs-api

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

I've started `registry-mirror` to demonstrate how a Content-Addressed file structure and P2P discovery, can bring a lot of speed improvements, specially when the bottleneck is low bandwidth/latency to the backbone, by connecting to more local peers that have the content that we are looking for.

Right now, the goal with `registry-mirror` is to have a very large IPFS node in the network with the entire npm and that keeps replicating it, while end user machines only download the modules they need (and if they agree, provide them to the network as well). Each end user will be able to get the latest state of the registry, through a IPNS hash, a mutable pointer, that changes each time the mirror is updated.

The nix package manager model layers perfectly on top of IPFS' MerkleDAG (https://github.com/ipfs/specs/tree/master/merkledag), it can be a very awesome transport for ied. An example of a package manager that uses IPFS to distribute the packages is GX https://github.com/whyrusleeping/gx - Still a WIP.

If this is interesting to you, join us at IRC Freenode #IPFS, it would be great to bounce more ideas! :)

The team has been hard at work designing a great training experience and we are proud to announce that the first live edition of the Node.js Secure Development Training will be on April 30, in Portland, OR.

Tickets are going to be released April 1st, register your interest today! As this event will have extremely limited seating!

https://ti.to/lift-security/node-sec-dev-portland

Never the less, your question is very pertinent! thank you!

http://2014.lxjs.org/ Tickets: https://ti.to/lxjs/2014

We are accepting contributions from the community to build the tools that get the job done efficiently and to audit modules, disclosing vulnerabilities in a responsible manner.