Update proposals/2836-threading.md

Co-authored-by: Matthew Hodgson <matthew@matrix.org>
kegan/msc/threading
Kegsay 4 years ago committed by GitHub
parent 4dcc8c62d4
commit 2b58fff463
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -1,6 +1,6 @@
### MSC2836: Threading ### 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 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 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 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 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 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. also contain the routing information with that relationship.

Loading…
Cancel
Save