Skip to content

Commit

Permalink
Acknowledge that we actually are changing the definition of read/unread
Browse files Browse the repository at this point in the history
  • Loading branch information
andybalaam committed Jul 17, 2023
1 parent be0f7ac commit e650a11
Showing 1 changed file with 5 additions and 7 deletions.
12 changes: 5 additions & 7 deletions proposals/4033-event-thread-and-order.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit e650a11

Please sign in to comment.