From 32eaa210583f5974a700d22996daf1ce48e0a30e Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Mon, 14 Jul 2025 09:45:27 -0600 Subject: [PATCH] Update proposals/4222-sync-v2-state-after.md Co-authored-by: Alexey Rusakov --- proposals/4222-sync-v2-state-after.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/4222-sync-v2-state-after.md b/proposals/4222-sync-v2-state-after.md index 461468364..604b74588 100644 --- a/proposals/4222-sync-v2-state-after.md +++ b/proposals/4222-sync-v2-state-after.md @@ -194,7 +194,7 @@ Since the current state of the room does not include the new state event, it's e ## Potential issues With the proposed API the common case for receiving a state update will cause the event to come down in both the -`timeline` and `state` sections, potentially increasing bandwidth usage. However, it is common for the HTTP responses to +`timeline` and `state_after` sections, potentially increasing bandwidth usage. However, it is common for the HTTP responses to be compressed, heavily reducing the impact of having duplicated data. Both before and after this proposal, clients are not able to calculate reliably exactly when in the