Bridging -- Code review for Pijul Nest about matrix-notepad

[KB1RD]

@notramo I don't think that this is something that makes sense to implement in Matrix Notepad directly.
BUT...
Matrix Notepad is built on top of Matrix and uses an event-based protocol that can be "spoken" by any program that can receive events from the Matrix server hosting the account. Matrix introduces the concept of bridges, which are designed to allow users from another chat platform to chat with users on Matrix. A bridge could be created that bridges edit events instead of chat messages using the same concept. Using this, the bridge (which would pose as a bot) could create a room and send insertion events for the remote patches. This would allow editing collaboratively through Matrix Notepad.

You mentioned that the original patch cannot be modified. Since Matrix Notepad does not redact old data, the original patch would not be deleted, only not rendered by the client. This is not desirable, though. I am working on multi-branch support as well as per-user branches. The bridge could make it so that all the users are forced into a suggestion branch. Again, the support is not present yet, but that's in the works.

I'll keep the issue open because it should be possible in the future. Bridging is something that I intend to support and I'm excited to see that there is a use for it!