Loro's rich text CRDT

I&#x27;m curious about this line describing REG:<p>&gt; The REG algorithm excels with its fast local update speeds and eliminate concerns about tombstone collection in CRDTs. For instance, if an operation has been synchronized across all endpoints, no new operations will occur concurrently with it, allowing it to be safely removed from the history.<p>If you remove these ops from history, does that remove the ability to time travel (per the home page &quot;An antidote to regret, enabling historical edits traversal&quot;) or merge branches? How can we be sure an operation is synchronized?<p>If dropping these ops is necessary for speed&#x2F;storage optimization but disables time-travel, is it possible to put the removed historical&#x2F;tombstone ops into a &quot;cold storage&quot; that&#x27;s optional and only loaded for time-travel use?

It&#x27;s great work improvising over Peritext using joseph&#x27;s latest CRDT work. Much needed literature in &quot;applying CRDTs for richtext&quot; space.<p>But I&#x27;m surprised why this one too hasn&#x27;t focussed a lot on rich-text block elements (like lists, tables &amp; sections) as much as it focussed on text attributes (like bold and italics).

Looks neat! Would there be a way of intercepting state and making &#x27;snapshots&#x27; into a more traditional format, like SQL, or even a JSON file?<p>It sounds like this defaults to the server storing the whole state in their binary format, ditto the client-side portion of it. Nothing wrong with the format, but this is an early project, and nobody wants their data in something that&#x27;s potentially unstable, or something that might get corrupted.

Slightly off-topic - I don&#x27;t think real-time collaboration is suitable for text-based formats. I believe collaboration similar to working with git is superior:<p>1. Fork the text<p>2. Submit proposal<p>3. Review<p>4. Merge&#x2F;Cancel<p>EDIT: To slightly expand on this - there are many reasons for this intuition - the main, IMO, is that people like to work on text privately before showing it to people. Also, the mental fear of your text interrupted by someone else. There might be even more reasons.

Would be nice to see cola included in the benchmarks: <a href="https:&#x2F;&#x2F;nomad.foo&#x2F;blog&#x2F;cola" rel="nofollow">https:&#x2F;&#x2F;nomad.foo&#x2F;blog&#x2F;cola</a>

Looks dope, could be nice for collaborative writing like a multi-author blog post or for docs.

Hmm, not helpful. I&#x27;m on iOS, so there is no console.<p>&gt; Application error: a client-side exception has occurred (see the browser console for more information).