Proposal: Versioned Collaborative Documents
summary
Proposal defines versioned collaborative documents that combine Google-Docs live editing with git-style fork and merge workflows by treating each document as a UUID-labeled append-only log of op-based CRDT updates. A doc’s owner picks a Home Server that stores the authoritative log and enforces permissions; users keep local optimistic logs, fork by copying logs to new doc IDs, and merge by appending missing updates with a diff/preview step. Practical issues discussed: compaction of huge keystroke logs, cherry-pick/history-hiding semantics, and integration with Yjs/Automerge-style tooling.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:49Core concepts
- 7:46Fork and merge in practice
- 12:18Platform design and Home Server
- 20:12Programming versioned docs
- 23:39Access control and user agency
- 27:55Compaction and history challenges
- 33:11Q&A
related talks
35mThe practical implementation of Documentation as Code
31mThe Next Millenium Document Format
24mHave You Gone MADR?
22mShifting Left, Shifting Right
29mData Diffing Based Software Architecture Patterns
11mLightning Talk: Repurposed Purpose: Using Git's DAG for Supply Chain Artifact Resolution
50mPijul: Version-Control Post-Git
44mArchitectural Practices for Greater Scalability and Innovation