From 6f411413af9ca44d1e015f2f7f413292726d4a3d Mon Sep 17 00:00:00 2001
From: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
Date: Mon, 6 Jun 2022 19:06:28 +0100
Subject: [PATCH] clarification to MSC2675 (#3829)

because this is confusing enough without outright lies
---
 proposals/2675-aggregations-server.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/proposals/2675-aggregations-server.md b/proposals/2675-aggregations-server.md
index b5dd501f..9a86ecbd 100644
--- a/proposals/2675-aggregations-server.md
+++ b/proposals/2675-aggregations-server.md
@@ -196,6 +196,10 @@ adds the related-to event in `original_event` property of the response.
 This way the full history (e.g. also the first, original event) of the event
 is obtained without further requests. See that MSC for further details.
 
+   * **Edited 2022-06-06**: This appears to be incorrect. MSC2676 contains
+     no reference to `original_event`, nor can I find any record of it ever
+     having done so.
+
 ### End to end encryption
 
 Since the server has to be able to aggregate relation events, structural
@@ -317,4 +321,4 @@ While this MSC is not considered stable, the endpoints become:
 
 None of the newly introduced identifiers should use a prefix though, as this MSC
 tries to document relation support already being used in
-the wider matrix ecosystem.
\ No newline at end of file
+the wider matrix ecosystem.