Viewing profile — czx111331

Perhaps the most important difference is that software — even after being purchased and used — remains relatively easy to patch, unlike a physical lock.

loro-prosemirror[1] offers much better support for integrating Loro with ProseMirror/Tiptap. In theory, loro-mirror could also be used to integrate Loro with other rich-text editor…

I believe that in the right contexts—specifically where eventual consistency is acceptable—the local-first paradigm is highly valuable and will gradually become mainstream. A major…

Is Bitcoin a "public sync" application by the definition?

The implementation can indeed combine multiple different CRDTs. Within Loro's internal implementation, each op does need to store a parent ID. However, as Seph mentioned, consecuti…

We are carefully stabilizing our encoding format and will have a clear storage format documentation introduced in version 1.0. I agree that a more transparent format can provide us…

Similar to OT, in certain scenarios, it's sufficient to ensure that only a subset of peers have the complete data, while others don't need the full history. For instance, in real-t…

> If you remove these ops from history, does that remove the ability to time travel (per the home page "An antidote to regret, enabling historical edits traversal") or merge branch…

Yes, it's agnostic to the network layers. The output of doc.exportFrom() is just a binary array.

We are addressing the CRDT downsides mentioned in the article at Loro: - Ever-growing state. This is no longer an issue. With OT-like CRDTs, you can discard unnecessary historical …

The code in the blog is from Vue Pinia, a state management library, and not from Loro. It serves as an example demonstrating that CRDTs can be modeled similarly. Thus, you might ex…

Nice work! However, it doesn't seem like a fair benchmark. It doesn't calculate and store the ops, nor does it store the actual text. To build a text CRDT with delta updates suppor…