From 71b223586803fba02e9b317eaf2ad778b3bd1878 Mon Sep 17 00:00:00 2001 From: Jonas Platte Date: Tue, 21 Feb 2023 18:38:48 +0100 Subject: [PATCH] Clarify that reply chain fallback for threads may not be present (#1439) --- changelogs/client_server/newsfragments/1439.clarification | 1 + content/client-server-api/modules/threading.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) create mode 100644 changelogs/client_server/newsfragments/1439.clarification diff --git a/changelogs/client_server/newsfragments/1439.clarification b/changelogs/client_server/newsfragments/1439.clarification new file mode 100644 index 00000000..ed05216d --- /dev/null +++ b/changelogs/client_server/newsfragments/1439.clarification @@ -0,0 +1 @@ +Clarify that reply chain fallback for threads may not be present. diff --git a/content/client-server-api/modules/threading.md b/content/client-server-api/modules/threading.md index 2a7f02d0..240ae33d 100644 --- a/content/client-server-api/modules/threading.md +++ b/content/client-server-api/modules/threading.md @@ -74,7 +74,7 @@ Clients which understand how to work with threads should simply do so, however c might not be aware of threads (due to age or scope) might not be able to helpfully represent the conversation history to its users. -To work around this, events sent by clients which understand threads include [rich reply](#rich-replies) +To work around this, events sent by clients which understand threads SHOULD include [rich reply](#rich-replies) metadata to attempt to form a reply chain representation of the conversation. This representation is not ideal for heavily threaded rooms, but allows for users to have context as to what is being discussed with respect to other messages in the room.