@martin Exactly that is what I'm dreaming of as well! Is there a place I can contribute to this vision? #localfirst
@holtwick Great! At the moment we’re still at the stage of making the individual implementations great before it makes sense to start the standardisation process. So I suggest you pick an implementation you like, use it, and help figure out how to make its sync protocol better. Both Automerge and Yjs have current projects to improve their respective sync protocols.
@martin Awesome, thanks. I'll take a look. Besides the "generic" implementation, I would personally like such a service to be content agnostic i.e. it should be rather "dumb" and all data passing should be E2EE. I guess "zero trust" is the right buzzword ;) I created such an implementation for my projects, maybe I find the time to wrap that up and present it in a blog article. Thanks for the initiative and inspiration. Great to see that such a vivid community is pushing these promissing ideas.
@holtwick I agree! Would love to read your thoughts if you write them up. We’re just about to spin up a project to develop a generic e2ee layer for Automerge that will work both with untrusted sync servers and p2p.
@martin As promised, the blog article describing my approach to sync for my #localfirst apps. The idea is pretty trivial and probably common practice, but well ... the simpler the better ;) Maybe it will give you a little inspiration anyway. The text is available in German and English. https://holtwick.de/en/blog/localfirst-resilient-sync
@swick @holtwick A partial answer is in this paper: https://eprint.iacr.org/2020/1281 — the algorithm offers similar security to MLS, but decentralised. We’re currently working on filling in the bits that are missing in that paper, especially the group membership algorithm
