From 109bfb2ddb3745842a42fff1d38d7a91623ea6cb Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Thu, 26 May 2022 20:19:04 -0600 Subject: [PATCH] Clarify how ignoring works for aggregations. --- 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 609611d2..02f4053a 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -1994,10 +1994,11 @@ its own, as the server will not have considered them. {{% /boxes/warning %}} {{% boxes/note %}} -Events from [ignored users](#ignoring-users) do not appear in the bundle or aggregation. -Clients will need to de-aggregate the events sent by ignored users to avoid them being -considered in counts. Similarly, servers must ensure they do not consider events from -ignored users when preparing a bundle for the client. +Events from [ignored users](#ignoring-users) do not appear in the bundle or aggregation +from the server, however clients might still have events from ignored users cached. Like +with normal events, clients will need to de-aggregate events sent by ignored users to +avoid them being considered in counts. Servers must additionally ensure they do not +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