mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-03-29 15:34:09 +02:00
Try to clarify redactions a bit
This commit is contained in:
parent
109bfb2ddb
commit
0d35037f14
|
|
@ -2001,10 +2001,11 @@ avoid them being considered in counts. Servers must additionally ensure they do
|
||||||
consider events from ignored users when preparing a bundle for the client.
|
consider events from ignored users when preparing a bundle for the client.
|
||||||
{{% /boxes/note %}}
|
{{% /boxes/note %}}
|
||||||
|
|
||||||
When an event is redacted, the relations attached to it remain. However, when an event
|
When a parent event is redacted, the events which pointed to that parent remain, however
|
||||||
which uses a relation is redacted then the relation is broken. Thus, the server needs
|
when an event which points at a parent is redacted then the relationship is broken.
|
||||||
to de-aggregate or disassociate an event from its parent when it is redacted. Clients
|
Therefore, the server needs to de-aggregate or disassociate the event once the relationship
|
||||||
with local aggregation should do the same.
|
is lost. Clients with local aggregation or which handle redactions locally should do the
|
||||||
|
same.
|
||||||
|
|
||||||
It is suggested that clients perform local echo on aggregations. For instance, aggregating
|
It is suggested that clients perform local echo on aggregations. For instance, aggregating
|
||||||
the event into a bundle optimistically until the server returns a failure or the client
|
the event into a bundle optimistically until the server returns a failure or the client
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue