This is an interesting use of the Matrix protocol. I like the many creative ways Matrix is being used outside the chat space, where its predominant use lies. However, I have several questions about this approach.
- What happens with E2EE when there are key exchange problems? (i.e. a server goes down and the account is moved)
- What happens when someone redacts a message? I assume you'd want to disable redactions for these rooms or you'll end up with broken update trees!
- How do you communicate clearly that any data you add is in the event chain forever? In Word and GDocs you can remove old revisions of a document, but I don't think you can in this system? That could be a feature, of course!
- What's the performance impact of such a system on a server editing reasonably large documents? If twenty people each edit ten to twenty documents you end up with quite a large set of state, especially over time!
- What happens with E2EE when there are key exchange problems? (i.e. a server goes down and the account is moved)
- What happens when someone redacts a message? I assume you'd want to disable redactions for these rooms or you'll end up with broken update trees!
- How do you communicate clearly that any data you add is in the event chain forever? In Word and GDocs you can remove old revisions of a document, but I don't think you can in this system? That could be a feature, of course!
- What's the performance impact of such a system on a server editing reasonably large documents? If twenty people each edit ten to twenty documents you end up with quite a large set of state, especially over time!