Introduction to Loro's Rich Text CRDT

Re:Introduction to Loro's Rich Text CRDT by mikebelanger on Tuesday January 23, 2024 @05:52PM (#39111102)

Looks neat! Would there be a way of intercepting state and making 'snapshots' into a more traditional format, like SQL, or even a JSON file?

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's potentially unstable, or something that might get corrupted.

[ Parent | on HN ]

Re:Introduction to Loro's Rich Text CRDT by CodeGroyper on Tuesday January 23, 2024 @06:22PM (#39111422)

Supposedly you can always make a deep copy or a backup of anything you have.

[ Parent | on HN ]

Re:Introduction to Loro's Rich Text CRDT by czx111331 on Wednesday January 24, 2024 @04:38AM (#39115438)

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 users with a better sense of control, and we will try to create a human-readable format for exporting CRDT data (the kind that includes operation history). As for the application state, Loro already supports direct export in json format.

[ Parent | on HN ]

Re:Introduction to Loro's Rich Text CRDT by mikebelanger on Friday January 26, 2024 @01:36PM (#39146176)

Ok, I appreciate you reaching back. And my bad, I didn't see that it already supports direct export of JSON.

[ Parent | on HN ]