News for hackers. Stuff that matters.

A comment on You don't need a CRDT to build a collaborative experience. Parent comment

Re:You don't need a CRDT to build a collaborative experience by btown on Thursday November 16, 2023 @12:15PM (#38292299)
Are you considering having a CRDT for each text block individually, or moving to a CRDT for the entire data model for a document? Really curious about the design approach here, especially insofar as there's now an external API that the data models need to service!
[ Parent | on HN ]
Re:You don't need a CRDT to build a collaborative experience by jitl on Thursday November 16, 2023 @12:22PM (#38292439)
It’s Complicated (tm), a hybrid of the two. Text content across multiple CRDT enabled blocks may be connected in a single logical CRDT, but the segment visible in any given block is stored in that block object, which maintains our permission system invariants. We’ll still support moving blocks to different pages, so one page may have a few different CRDTs visually interleaved.

API consumers are unaffected. Likely we’ll support API updates of text as best-effort diff-match-patch of the text on our side applied as CRDT ops.

[ Parent | on HN ]
Re:You don't need a CRDT to build a collaborative experience by npunt on Thursday November 16, 2023 @01:51PM (#38293685)
always great hearing your perspective on the notion text engine jake, thanks for taking the time to explain everything!
[ Parent | on HN ]