Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PeerPad – A realtime P2P collaborative editing tool powered by IPFS

peerpad.net

Post reply on HN
Print view View original

1–10 of 25 posts

Re: PeerPad – A realtime P2P collaborative editing tool powered by IPFS

#3

Post by wscott »

It didn't work for me, but might be busy.

This is IPFS and it theory will use the javascript IPFS server in your browser unless it can find a local IPFS daemon on your machine. (Or perhaps it uses one of the gateways?)

How do they prevent the data from disappearing if everyone disconnects?

Re: PeerPad – A realtime P2P collaborative editing tool powered by IPFS

#6

Post by diggan »

wscott wrote: post #3

It didn't work for me, but might be busy. This is IPFS and it theory will use the javascript IPFS server in your browser unless it can find a local IPFS daemon on your machine. (Or perhaps it uses one of the gateways?) How do they prevent the data from disappearing if everyone disconnects?

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

Re: PeerPad – A realtime P2P collaborative editing tool powered by IPFS

#7

Post by diggan »

wodenokoto wrote: post #2

Where are documents stored? Browser cache on each client?

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

Re: PeerPad – A realtime P2P collaborative editing tool powered by IPFS

#8

Post by pgte »

wscott wrote: post #3

It didn't work for me, but might be busy. This is IPFS and it theory will use the javascript IPFS server in your browser unless it can find a local IPFS daemon on your machine. (Or perhaps it uses one of the gateways?) How do they prevent the data from disappearing if everyone disconnects?

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

Re: PeerPad – A realtime P2P collaborative editing tool powered by IPFS

#9

Post by espadrine »

pgte wrote: post #8
wscott wrote: post #3

It didn't work for me, but might be busy. This is IPFS and it theory will use the javascript IPFS server in your browser unless it can find a local IPFS daemon on your machine. (Or perhaps it uses one of the gateways?) How do they prevent the data from disappearing if everyone disconnects?

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

How would remote pinning work?

If I understand correctly, each keystroke in the pad generates a new snapshot, which has a distinct IPFS ID.

Should the remote pinning service publish a list of all IPFS IDs on the p2p network, and store each individual document (each one keystroke away from the previous one) in the history graph?

Should it keep the complete list of CRDT operations, and map IPFS IDs to CRDT operations IDs, so that it can reconstruct any document when it is requested?

Is there a way to use the properties of CRDT that I am not seeing?

Post reply on HN