Yep. I've done something very similar on top of Diamond Types for a little personal wiki. This page[1] is synced between all users who have the page open. Its a

Yep. I've done something very similar on top of Diamond Types for a little personal wiki. This page[1] is synced between all users who have the page open. Its a remarkably small piece of code, outside of the CRDT library itself (which is in rust via wasm). The way it works is: - On page load, the server sends the whole CRDT document to the browser, and the server streams changes from that point onwards. - When a change happens in the browser, it makes that change locally then and sends anything the server doesn't know about upstream. - Whenever the server finds out about a new change, it re-broadcasts that change to any subscribed browser streams. I'm using the braid HTTP protocol for changes - but we could easily switch to a SSE or websocket solution. It doesn't really matter. At the moment I'm just using flat files for storage, but there's nothing stopping you using a database instead, except that its a bit awkward to use efficient CRDT packing techniques in a database. [1] https://wiki.seph.codes/hn https://wiki.seph.codes/hn Code is here, if anyone is interested. The whole thing is a few hundred lines all up: https://github.com/josephg/diamond-types/tree/0cb5d7ecf49364a0a8c0e52c5b325d5dafcb883e/wiki https://github.com/josephg/diamond-types/tree/0cb5d7ecf49364...