Fun academic find: the core idea of server reconciliation (a general approach to real-time collaboration that's simpler than Operational Transformation or CRDTs) already appears in an MIT tech report from 1985.
I learned of this from the first paper on collaborative text editing (dl.acm.org/doi/abs/10.1145/6…), which cites the idea but claims it won't work for text. Instead they introduce Operational Transformation, which led to a lot of academic work but is more complicated.
1
2
157
We know now that the server reconciliation approach does work for text, so long as you assign each character an ID instead of trying to use array indexes: mattweidner.com/2025/05/21/t…
1
6
128
From the ~1st collab text editing paper: if two users do "delete char @ index 7" concurrently, no serial ordering gives the correct answer. So they abandon serializability, leading to OT/CRDTs. But if you rephrase the ops as "delete char @ <per-char id>", both serial orders work!
1
201
For many collaborative apps, though, you can get away with just serializing all users' ops. E.g., apply ops in the order a server receives them. This strategy appears in @replicache and in @tan_stack DB (taking over from ElectricSQL v0's fancier CRDT-based strategy).
1
2
162
More on this simple path to collaborative apps, as an alternative to the Operational Transform / CRDT rabbit hole, in my recent DWeb Seminar talk: docs.google.com/presentation…
142
I made a guest post on @powersync_'s blog: powersync.com/blog/collabora…
It describes a demo we made of collaborative text editing on top of PowerSync's DB sync engine, using character IDs & totally-ordered updates in a DB table (w/o CRDTs).
Matthew Weidner retweeted
Watch @MatthewWeidner3 talk about collaborative text editing without CRDTs or OT. youtu.be/5CFrpd0sG-g?si=x5xA…
Matthew Weidner retweeted
"Collaborative text editing without CRDTs or OT"
Awesome talk from @MatthewWeidner3 on how you don't need CRDTs to build collaborative text editing.
New blog post: "Collaborative Text Editing without CRDTs or OT". It describes what I hope is a simpler and more flexible approach to the hardest part of a collaborative app, text editing.
Link: mattweidner.com/2025/05/21/t…
I'll also talk about it at Local-First Conf next week.
Together with my last post (mattweidner.com/2024/06/04/s…), this should let you build central-server collaborative apps with *no* tricky CRDT or OT algorithms! (Though CRDT ideas are still helpful.)
I look forward to talking about some new ideas from my work at Common Curriculum & CMU!
We’re excited to announce that @MatthewWeidner3, PhD student at CMU, will be speaking at Local-First Conf 2025! Matthew will share a surprisingly simple approach to collaborative text editing—no CRDTs or OT required.
9
523
Johannes is a great host, and this was a fun discussion. Check it out & spread the word about localfirst.fm!
The blog post we walk through is mattweidner.com/2024/06/04/s…
Episode #14 is out.
Matthew Weidner (@MatthewWeidner3) on architectures for central server collaboration including CRDT, OT and event-sourcing.
I'm happy to announce that I've joined Common Curriculum (@MakeCurriculum) as a software developer. It is a collaborative app that helps teachers create their lesson plans, and I am excited to see what we'll get up to!
2
12
517
New blog post: Architectures for real-time collaborative apps using a central server. It includes classic CRDT/OT approaches, why those might be overkill, and a classification table for existing apps/tools.
mattweidner.com/2024/06/04/s…










