Martin Kleppmann

I agree that we need a solution for this problem, but I'm not totally convinced that this approach is the best one. Special-casing the initialisation change to make it deterministic...

@DiamondYuan That would be a big API change, which I'm not keen on. I think we can change the semantics for concurrently created objects on the same key without otherwise...

I have spent a while thinking about this too, and I also think that a single document sequence with marker characters is the way to go. If you represent a...

> What happens if the element cursor was at got removed ? Would index somehow be restored via tombstone ? Yes, currently tombstones are retained indefinitely anyway, so the element...

> For what it's worth I chose to avoid open / close style markers that introduce complication due to nesting I agree with that: in a concurrent editing setting it...

Update: @pvh's initial implementation of the OAFS model is now in `test/text_test.js` as of #238. We can discuss later whether to make it available as part of Automerge, or whether...

Hi @begor, thanks for this. The browsertest failure can be ignored (it's been flaky since I moved from Travis CI to GitHub Actions and I haven't yet figured out how...

> Would this proposal be looking to extend the protocol to cover multiple documents? Yes. In the simplest case, this could use essentially the current sync protocol, with each message...

Other ideas that have come up: * As part of the multi-doc sync protocol it might also be useful to include support for syncing arbitrary binary blobs. That way, you...

> How would that play out with RDBMS that generate their IDs? In systems where you have a single authoritative DB server it might make sense to let that server...