[WIP] MSC4059: Mutable event content #4059
Conversation
turt2live
added
requires-room-version
|
|
||
| **TODO**: Detail. | ||
|
|
||
| Just send edits, or regular state updates!? |
There was a problem hiding this comment.
Sending edits (deltas) seems like a good idea.
It may lower event's size substantially (given the difference between event's content and made changes is great, such as type corrections, which I'd expect to be the most used case).
E.g., original text: "The wolrd is round" , changes [del 6(l), del 7(r), add 5 r, add 6 r] or [cursor at 8 (r), del, del, r, l].
new text: "The world is round".
I.e., we could use a CRDT data model to represent edits.
What I like about this approach is how we have persistency. If you reply to one's event you want it to point to exact content you referred to. Later on this content may evolve, but the pointer is at that particular version in history.
Makes us safe from subversion of semantics.
E.g., one posted "I love petting cats!" and you reply "Me too, would do it all day long!". Later original poster could change it to "I love torturing cats!", but your semantics are not subverted, as it points to the exact snapshot that's about petting.
There was a problem hiding this comment.
We would not need a full-fledged CRDT if a message is edited only from one device, having it as a simple log of edits. But given you have multiple devices there may inevitably be a case where you make edits from both. E.g., it's a darn long-form message one works on for a couple of days from both your laptop and mobile (while enjoing comfort of whatever one's sitting on).
Rendered