From c8e39c10b7d50030282fa6184e93ce9fb4016276 Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Tue, 28 Nov 2023 11:22:28 +0000 Subject: [PATCH] Use close to the original wording for the 'recurse' part of the 'in the thread' definition --- content/client-server-api/modules/receipts.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/client-server-api/modules/receipts.md b/content/client-server-api/modules/receipts.md index 470c099b..e32ab18e 100644 --- a/content/client-server-api/modules/receipts.md +++ b/content/client-server-api/modules/receipts.md @@ -140,9 +140,10 @@ room and thus deserve their own read receipts and notification counts. An event considered to be "in a thread" if: * 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 - up the chain of relations. (Implementations should not recurse to arbitrary - depth: a maximum of 3 hops is recommended to cover indirect relationships.) +* Following the event relationships, it has a parent event which references + the thread root with a `rel_type` of `m.thread`. Implementations should + 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 timeline". When referring to the main timeline as a thread (e.g. in receipts