Weird new (to Twitter) paper with and . The title basically tells the whole story:
Merge What You Can, Fork What You Can’t:
Managing Data Integrity in Local-First Software
riffle.systems/papoc22.pdf
In a few more words...
Conversation
Nice idea! So you can delay merging conflicts, but can you change how they eventually resolve? I.e. cherry pick the winner. That is the key property of version control that so far I haven't seen done in CRDTs.
2
5
Yes, that’s exactly right. Ideally the app exposes some tools for figuring out what the difference is and then helping you patch things up.
In the meantime, if everyone’s seen the same events then at least you all agree on what the different branches are.
2
6
I'm doing related work. What conferences are interested in this? There doesn't seem to be a natural home for it. Maybe we need to run a workshop ourselves.
1
3
So there's workshop on local first at ECOOP in June. I'll be there. I've been interested in this problem for a while (18 years), great to see progress!
2
8
Other than the PLF workshop at ECOOP—which I sadly won't be able to attend—I think that PaPoC is the best venue I've seen for this kind of conceptual work in this space.
I suspect that a paper really fleshing out the theory could get into a distributed computing venue (maybe OPODIS?) and a good implementation paper wouldn't be unwelcome at a database conference like SIGMOD. It's probably on the periphery of both of them, though.
What would your (asking you all) ideal workshop topic be?
1
3
I'd be really interested in a workshop on "end-to-end sync", covering everything from "how do you make an efficient CRDT" to "what's a good conflict UI for end-users". The basic (provocative) thesis is something like "giving sync the respect it deserves" all the way up the stack.
2
3
Show replies