From e650a11aa5db1c53bd0a41a983377993e979fa9a Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Mon, 17 Jul 2023 13:29:11 +0100 Subject: [PATCH] Acknowledge that we actually are changing the definition of read/unread --- proposals/4033-event-thread-and-order.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/proposals/4033-event-thread-and-order.md b/proposals/4033-event-thread-and-order.md index 72d6cbb6c9..f80c8cd5ce 100644 --- a/proposals/4033-event-thread-and-order.md +++ b/proposals/4033-event-thread-and-order.md @@ -175,15 +175,13 @@ to be explicit about what "read up to" means, using the above definition. ### Definition of read and unread events -We propose that the definition of whether an event is read should be unchanged, -but this note should be added: +We propose that the definition of whether an event is read should include the +original definition plus the above definition of *after*, and also include this +clarification: > (Because the receipt itself contains the `order` of the pointed-to event, -> there is no need to examine the pointed-to event, so it is sufficient to -> compare the `order` of the event in question with the `order` in the -> receipt.) - -And the above definition of *after* should be included. +> there is no need to examine the pointed-to event: it is sufficient to compare +> the `order` of the event in question with the `order` in the receipt.) ### Redacted events