From 3acc7380e6d69e67d69b7f81624d4e8e3650ed9c Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Wed, 6 Aug 2025 15:45:44 +0100 Subject: [PATCH] Clarify that the server should also only consider **valid** replacements --- content/client-server-api/modules/event_replacements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/client-server-api/modules/event_replacements.md b/content/client-server-api/modules/event_replacements.md index 2e36e40e..e42dacf8 100644 --- a/content/client-server-api/modules/event_replacements.md +++ b/content/client-server-api/modules/event_replacements.md @@ -195,7 +195,7 @@ given event (for example, if an event is edited multiple times). These should be [aggregated](#aggregations-of-child-events) by the homeserver. The aggregation format of `m.replace` relationships gives the **most recent** -replacement event, formatted [as normal](#room-event-format). +valid replacement event, formatted [as normal](#room-event-format). The most recent event is determined by comparing `origin_server_ts`; if two or more replacement events have identical `origin_server_ts`, the event with the