From 058e97e5f11971d1f9d508b7b90b8f02beae305a Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Tue, 28 Nov 2023 11:27:56 +0000 Subject: [PATCH] Define the thread root --- content/client-server-api/modules/threading.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/client-server-api/modules/threading.md b/content/client-server-api/modules/threading.md index 2d3abef5..b6e11821 100644 --- a/content/client-server-api/modules/threading.md +++ b/content/client-server-api/modules/threading.md @@ -12,7 +12,7 @@ as by providing some context to what is going on in the thread but keeping the f history behind a disclosure. Threads are established using a `rel_type` of `m.thread` and reference the -*thread root*. It is not possible to create a thread from an event which itself +*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