From 3c439d09f99ddc5cdf717bada581d141a8bbf744 Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Tue, 28 Nov 2023 11:24:50 +0000 Subject: [PATCH] Remove note about thread roots being displayed in a thread --- content/client-server-api/modules/receipts.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/content/client-server-api/modules/receipts.md b/content/client-server-api/modules/receipts.md index e32ab18e6..54c8c7cf4 100644 --- a/content/client-server-api/modules/receipts.md +++ b/content/client-server-api/modules/receipts.md @@ -150,10 +150,7 @@ timeline". When referring to the main timeline as a thread (e.g. in receipts and notifications counts) a special thread ID of `main` is used. Thread roots are considered to be in the main timeline, as are events that are -related to a thread root via non-thread relations. Note that clients providing a -single-thread view will probably want to include thread roots and some of their -child events (e.g. reactions) in that view, even though from a receipt point of -view they are not part of that thread. +related to a thread root via non-thread relations. The following is an example DAG for a room, with dotted lines showing event relationships and solid lines showing topological ordering.