From 3b2146c875c25ad87f5424af4294c169957bc3a0 Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Tue, 5 Dec 2023 16:28:05 +0000 Subject: [PATCH] Batch receipts by thread as well as room (#1685) --- changelogs/client_server/newsfragments/1685.clarification | 1 + content/client-server-api/modules/receipts.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) create mode 100644 changelogs/client_server/newsfragments/1685.clarification diff --git a/changelogs/client_server/newsfragments/1685.clarification b/changelogs/client_server/newsfragments/1685.clarification new file mode 100644 index 00000000..9daf762e --- /dev/null +++ b/changelogs/client_server/newsfragments/1685.clarification @@ -0,0 +1 @@ +Clarify that read-receipts should be batched by thread as well as room. diff --git a/content/client-server-api/modules/receipts.md b/content/client-server-api/modules/receipts.md index 54c8c7cf..d8733e19 100644 --- a/content/client-server-api/modules/receipts.md +++ b/content/client-server-api/modules/receipts.md @@ -208,7 +208,7 @@ event when the user expands that thread. #### Server behaviour -For efficiency, receipts SHOULD be batched into one event per room +For efficiency, receipts SHOULD be batched into one event per room and thread before delivering them to clients. Some receipts are sent across federation as EDUs with type `m.receipt`. The