From a843cad285f9b302f12060631bda58d289be10ee Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Mon, 11 Dec 2023 13:00:59 +0000 Subject: [PATCH] Clarify that threads can be created based on replies (#1687) Signed-off-by: Andy Balaam Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> --- changelogs/client_server/newsfragments/1687.clarification | 1 + content/client-server-api/modules/threading.md | 8 +++++--- 2 files changed, 6 insertions(+), 3 deletions(-) create mode 100644 changelogs/client_server/newsfragments/1687.clarification diff --git a/changelogs/client_server/newsfragments/1687.clarification b/changelogs/client_server/newsfragments/1687.clarification new file mode 100644 index 00000000..09bacd28 --- /dev/null +++ b/changelogs/client_server/newsfragments/1687.clarification @@ -0,0 +1 @@ +Clarify that threads can be created based on replies. diff --git a/content/client-server-api/modules/threading.md b/content/client-server-api/modules/threading.md index b6e11821..f082f389 100644 --- a/content/client-server-api/modules/threading.md +++ b/content/client-server-api/modules/threading.md @@ -14,9 +14,11 @@ history behind a disclosure. Threads are established using a `rel_type` of `m.thread` and reference the *thread root* (the main timeline event to which the thread events refer). It is not possible to create a thread from an event which itself is the child of an event relationship (i.e., one with an `m.relates_to` -property). It is therefore also not possible to nest threads. All events in a -thread reference the thread root instead of the most recent message, unlike rich -reply chains. +property with a `rel_type` property - see [Relationship types](#relationship-types)). +It is therefore also not possible to nest threads. + +Unlike rich reply chains, all events in a thread reference the thread root +instead of the most recent message. As a worked example, the following represents a thread and how it would be formed: