peer-pad

Another one for the list: https://github.com/ipfs-shipyard/peer-pad Demo here: http://dev.peerpad.net/ (this version will launch soon as soon as we complete the “pinning” / backup link to ipfs-cluster and make some UI tweaks) Built with: https://github.com/peer-base/peer-base

Look at the IPFS Pubsub and Y.js integration, that e.g. PeerPad uses to build distributed text editing: https://github.com/ipfs-shipyard/peer-pad/blob/master/docs/A...

Remote pinning would work as any other node that you give the permissions to read the feed. This node would follow the CRDT changes, persisting them locally. Each keystroke produces a change in the CRDT, which is then eventually propagated to all participating nodes. Each CRDT message is signed and encrypted before being sent over the IPFS pubsub network. This protocol is not IPFS-specific, but there are plans to change this: https://github.com/ipfs-shipyard/peerpad/issues/107 The snapshotting occurs over IPFS, producing a static and encrypted self-contained snapshot, published over IPFS. It is possible to access the CRDT properties inside the core library, where the CRDT is formed: https://github.com/ipfs-shipyard/peerpad-core/blob/master/sr... . This could be exposed if you would require it..

Hi everyone! 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 u

If you don't mind me asking, what browser and version did you use? It uses WebRTC for peer-to-peer communication, which is yet unsupported / untested in some browsers. To answer your question: The collaborative data is saved locally by every participating peer. There are plans to add remote tracking and pinning, increasing the persistence and availability guarantees: https://github.com/ipfs-shipyard/peerpad/issues/90

Currently, yes, it's stored in the client. We have some plans for being able to select a pinning service for making sure the data persists: https://github.com/ipfs-shipyard/peerpad/issues/90

Hm, that's no good. Did you run in a private tab? It also take some seconds before the node is initialized and ready to be used. Currently, PeerPad only uses the JavaScript implementation of IPFS (https://github.com/ipfs/js-ipfs) but using a local daemon if it exists makes sense. > How do they prevent the data from disappearing if everyone disconnects? Right now, we're not preventing that. You'll have to be online to share the content (or have someone else pin the content). We do have a open issue for being able to select a pinning service, which would solve this issue: https://github.com/ipfs-shipyard/peerpad/issues/90

Great idea! Created a issue for tracking it: https://github.com/ipfs-shipyard/peerpad/issues/106 Thanks :)