-
- a mergeable CRDT tombstone - aka write a CRDT tombstone that is an empty map so that it can be merged with the concurrent update
-
I've been meaning to experiment with `diamond-types` in Helix which already uses Ropey + an [OT `Transaction`](https://github.com/helix-editor/helix/blob/master/helix-core/src/transaction.rs) to apply…
-
Hey!
I've been reading a bunch of stuff about creating multiplayer collaborative experiences. Started out reading Evan Wallace's posts on the Figma blog, then read some more technical literature, d…
f0rr0 updated
2 years ago
-
**Is your feature request related to a problem? Please describe.**
Right now, if I'm working on a topic with other people, I have to present my screen, or they need to refresh their screen whenever I…
-
### Problem
ipywidgets are currently collaborative in the sense that a change to a widget made in a frontend will propagate to every other frontend, but no conflict resolution in the change is done…
-
CRDTs can only be deleted as if they are bucket/key referencing. Actual deletion is possible with something such as `curl -XDELETE http://localhost:8098/types/maps/buckets/tests/keys/test_item` rather…
-
Since CRDTs can be CPU-intensive, I'm wondering if we could run all the Rust code in a separate thread, and have an async Python API that would not block while waiting for the CRDT operations to compl…
-
After handoff, the operations may be applied twice. This is because, logging_vnode does the handoff and gets the operations to the log. materializer_vnode does the handoff independently, and caches th…
-
-
I really want to push the limits of what a mobile web application is capable of. I want to help power the future of offline-first collaborative applications using cutting edge techniques.
CRDTs def…