From 2b58fff4631a2b645a166d14660517e1d964cc0f Mon Sep 17 00:00:00 2001 From: Kegsay Date: Wed, 28 Oct 2020 22:26:13 +0000 Subject: [PATCH] Update proposals/2836-threading.md Co-authored-by: Matthew Hodgson --- proposals/2836-threading.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/2836-threading.md b/proposals/2836-threading.md index cef86cfa..fb4e9e07 100644 --- a/proposals/2836-threading.md +++ b/proposals/2836-threading.md @@ -1,6 +1,6 @@ ### MSC2836: Threading -*This MSC supersedes https://github.com/matrix-org/matrix-doc/issues/1198 * +*This MSC probably supersedes https://github.com/matrix-org/matrix-doc/issues/1198* Matrix does not have arbitrarily nested threading for events. This is a desirable feature for implementing clones of social media websites like Twitter and Reddit. The aim of this MSC is to define the simplest possible API shape to implement threading @@ -193,4 +193,4 @@ Justifications: which the server is unaware of if the sender was on another homeserver. For this reason, we need to contain routing information *somewhere* so servers can retrieve the event and continue navigating the thread. As the client and server already have the event which contains a relationship to another event inside an unknown room, the simplest option is to - also contain the routing information with that relationship. \ No newline at end of file + also contain the routing information with that relationship.