From a00e70ed0481ba7726efd94d00c804ffb732f387 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Wed, 8 Jun 2022 14:58:44 -0600 Subject: [PATCH] Fix warning about server-side aggregation/bundling --- content/client-server-api/_index.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index e294a9d9..58384dcd 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -2026,8 +2026,10 @@ likely using the transaction ID as a temporary event ID until a proper event ID {{% boxes/warning %}} Due to history visibility restrictions, child events might not be visible to the user -if they are in a section of history the user cannot see. This can mean inaccurate aggregations -for events that are "out of range". +if they are in a section of history the user cannot see. This means any bundles which would +normally include those events will be lacking them and the client will not be able to +locally aggregate the events either — relating events of importance (such as votes) should +take into consideration history visibility. Additionally, if the server is missing portions of the room history then it may not be able to accurately aggregate the events.