From 0d35037f141726e4eb451fbc17a81e70a2cca5e9 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Thu, 26 May 2022 20:21:30 -0600 Subject: [PATCH] Try to clarify redactions a bit --- content/client-server-api/_index.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index 02f4053a..fc23d2cb 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -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. {{% /boxes/note %}} -When an event is redacted, the relations attached to it remain. However, when an event -which uses a relation is redacted then the relation is broken. Thus, the server needs -to de-aggregate or disassociate an event from its parent when it is redacted. Clients -with local aggregation should do the same. +When a parent event is redacted, the events which pointed to that parent remain, however +when an event which points at a parent is redacted then the relationship is broken. +Therefore, the server needs to de-aggregate or disassociate the event once the relationship +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 the event into a bundle optimistically until the server returns a failure or the client