✳flâneur — a map of the web's best reading
Peritext: A CRDT for Rich-Text Collaboration
inkandswitch.com · 11,021 words · saved by 9 readers
Collaboration on rich text is hard to model with plain-text approaches. We review the challenges and how to construct a CRDT for rich text.
In a real-time collaborative editor such as Google Docs, every keystroke typed into a document is immediately visible to the other collaborators. While this can be very convenient, such real-time (or synchronous ) collaboration is not always what users want. We interviewed eight people who regularly collaborate professionally on documents such as news articles, and several told us that they found real-time collaboration a stressful experience: they felt performative, self-conscious of others witnessing their messy work-in-progress, or irritated when a collaborator acted on suggestions before t
Explore this link on the map →saved by
- Cypress Williams
- Evan Cater
- CJ Quines
- Chloe Yan
- Eden Chan
- Sudarsh K
- Dhruvik Sanjay Parikh
- Vincent Huang
- Yueh Han Huang
related reading
- Introduction to Loro's Rich Text CRDT – Loroloro.dev
- CRDT: Text Buffer - Made by Evanmadebyevan.com
- Upwelling: Combining real-time collaboration with version control for writers.inkandswitch.com
- CRDTs go brrrjosephg.com
- You don't need a CRDT to build a collaborative experience | Hacker Newsnews.ycombinator.com
- An Interactive Intro to CRDTs | jakelazaroff.comjakelazaroff.com
- You don't need CRDTs for collaborative experiences — /dev/knillzknill.io
- Designing Data Structures for Collaborative Apps - Matthew Weidnermattweidner.com
- Idea Listjzhao.xyz
- Data Laced with History: Causal Trees & Operational CRDTs — Archagon Was Herearchagon.net
- Potluck: Dynamic documents as personal softwareinkandswitch.com
- About CRDTs • Conflict-free Replicated Data Typescrdt.tech