Clarify that threads can be created based on replies (#1687)
Signed-off-by: Andy Balaam <andy.balaam@matrix.org> Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
This commit is contained in:
parent
3b2146c875
commit
a843cad285
2 changed files with 6 additions and 3 deletions
|
@ -0,0 +1 @@
|
||||||
|
Clarify that threads can be created based on replies.
|
|
@ -14,9 +14,11 @@ history behind a disclosure.
|
||||||
Threads are established using a `rel_type` of `m.thread` and reference the
|
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
|
*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`
|
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
|
property with a `rel_type` property - see [Relationship types](#relationship-types)).
|
||||||
thread reference the thread root instead of the most recent message, unlike rich
|
It is therefore also not possible to nest threads.
|
||||||
reply chains.
|
|
||||||
|
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:
|
As a worked example, the following represents a thread and how it would be formed:
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue