Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-04-15 23:54:10 +02:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Use close to the original wording for the 'recurse' part of the 'in the thread' definition

Browse source
This commit is contained in:
Andy Balaam 2023-11-28 11:22:28 +00:00
parent 19a9446185
commit c8e39c10b7
1 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
content/client-server-api/modules/receipts.md
View file

@ -140,9 +140,10 @@ room and thus deserve their own read receipts and notification counts. An event
considered to be "in a thread" if: considered to be "in a thread" if:
* It has a `rel_type` of `m.thread`, or * It has a `rel_type` of `m.thread`, or
* It has a parent event with this `rel_type`, or a parent of a parent, or further * Following the event relationships, it has a parent event which references
up the chain of relations. (Implementations should not recurse to arbitrary the thread root with a `rel_type` of `m.thread`. Implementations should
depth: a maximum of 3 hops is recommended to cover indirect relationships.) not recurse infinitely, though: a maximum of 3 hops is recommended to
cover indirect relationships.
Events not in a thread but still in the room are considered to be in the "main Events not in a thread but still in the room are considered to be in the "main
timeline". When referring to the main timeline as a thread (e.g. in receipts timeline". When referring to the main timeline as a thread (e.g. in receipts