From 0dd2881c098526d453a12971ab578a46e39181f0 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Fri, 12 Jan 2024 16:36:07 -0700 Subject: [PATCH] Update proposals/4089-delivery-receipts.md Co-authored-by: Denis Kasak --- proposals/4089-delivery-receipts.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/proposals/4089-delivery-receipts.md b/proposals/4089-delivery-receipts.md index 52580b3f..4d9ff380 100644 --- a/proposals/4089-delivery-receipts.md +++ b/proposals/4089-delivery-receipts.md @@ -58,8 +58,9 @@ Content-Type: application/json The server then implies `ts` and sends the resulting EDU to the target event's origin server. The delivery receipt must only be routed to the target event sender. -An `m.read[.private]` receipt does *not* imply delivery, but rather that a client either does not -support delivery receipts or was not able to decrypt the message. +Receiving a `m.read[.private]` receipt without a delivery receipt does *not* imply +delivery, but rather that a client either does not support delivery receipts or was not +able to decrypt the message. Clients are welcome to implement additional requirements before sending a delivery receipt. For example, a user setting to disable delivery receipts in public rooms specifically, or all rooms the user is in.