|
|
|
@ -67,7 +67,11 @@ events.
|
|
|
|
Relations may be redacted like any other event.
|
|
|
|
Relations may be redacted like any other event.
|
|
|
|
|
|
|
|
|
|
|
|
The `m.relates_to`.`rel_type` and `m.relates_to`.`event_id` fields should
|
|
|
|
The `m.relates_to`.`rel_type` and `m.relates_to`.`event_id` fields should
|
|
|
|
be preserved over redactions, so that clients can distinguish redacted edits
|
|
|
|
be preserved over redactions, so that clients can still distinguish
|
|
|
|
|
|
|
|
redacted relations from other redacted events of the event type.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
One example is telling redacted edits (as proposed in
|
|
|
|
|
|
|
|
[MSC 2676](https://github.com/matrix-org/matrix-doc/pull/2676)) apart from
|
|
|
|
from normal redacted messages, and maintain reply ordering.
|
|
|
|
from normal redacted messages, and maintain reply ordering.
|
|
|
|
|
|
|
|
|
|
|
|
FIXME: synapse doesn't do this yet
|
|
|
|
FIXME: synapse doesn't do this yet
|
|
|
|
|