Does the network seem thin up here? Collaborating with mountaintop mesh networks
summary
Claims that operational transform cannot safely decentralize for text so a peer‑to‑peer editor uses CRDTs instead and builds an LSQ CRDT (an ordered tree sequence) that yields log‑time inserts, avoids tombstone bloat, and converges across many peers. Implementation notes: JavaScript prototypes, links and GitHub in slides, and reliance on peer discovery/relaying like libp2p for transport. A short demo editor exists showing offline edits sync to the same result with no central server.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:57Digital Nomads
- 3:55Tools
- 8:41Merge Changes
- 10:45Grocery Shopping
- 14:15Sandwiches
- 20:17Preconditions tombstones
- 23:04CRDT
- 27:00Advantages
- 28:10LCQ Tree
- 29:01Topology
- 30:44Conclusion
related talks
49mWhat CRDTs, distributed editing and the speed of light means to your writer friends
13mHow to make a real-time collaborative text editor in 5 easy steps!
22mHappily Ever After: A CRDT Fairy Tale
23mBuilding Offline and Real-Time Applications - The Magic of CRDTs
32mCRDT and other new ideas for client-server communication
20mThe disintermediated web
30mEverything's better with friends
30mDHT, BFT, OMG: Know Your Building Blocks for Decentralized Applications