Martin Kleppmann

@steida Cryptography is good for authenticating the author of a change, by signing it with the author's private key. That can be easily be done outside of Automerge, but it's...

> If someone makes a change that they are not supposed to do, remove their public key from the encrypted document so they lost access to it. That doesn't prevent...

Hi @MeneDev, unfortunately the patch callback is called after the internal state of Automerge has already been updated, so by this point it's too late to stop the update from...

Hi @CodingDive, thanks for the feedback! Yes, I can imagine that is frustrating. Great idea to provide more visibility into what is going on inside Automerge. How do you think...

Thanks @pvh and @dan-weaver for being so responsive. I hope you don't mind me chiming in. Let's try to reduce your issue to a single message exchange, without all the...

> That is, sync1 generates the message "Hello, I'm an empty document (with zero changes), there have been no new changes since our last sync, and I don't need anything...

I think this is a great idea and a very useful feature. There are just some details about which I'm not yet sure. How do you think the API for...

Yes, I think it would be a good idea for the document to have a list of views that get maintained incrementally, as that will allow for better performance optimisations....

Thank you @dmonad for chiming in. I have looked at this a bit further, with help from @josephg, and found that Yjs can also exhibit interleaving when list elements are...

I have started working through this, but I must admit I find it quite hard to follow what is going on with all the EventEmitters, as they result in very...