mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-03-26 13:04:10 +01:00
Fix warning about server-side aggregation/bundling
This commit is contained in:
parent
13a43c05be
commit
a00e70ed04
|
|
@ -2026,8 +2026,10 @@ likely using the transaction ID as a temporary event ID until a proper event ID
|
||||||
|
|
||||||
{{% boxes/warning %}}
|
{{% boxes/warning %}}
|
||||||
Due to history visibility restrictions, child events might not be visible to the user
|
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
|
if they are in a section of history the user cannot see. This means any bundles which would
|
||||||
for events that are "out of range".
|
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
|
Additionally, if the server is missing portions of the room history then it may not be
|
||||||
able to accurately aggregate the events.
|
able to accurately aggregate the events.
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue