Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-27 05:24:10 +01:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity

Apply suggestions from code review

Browse source 
Co-authored-by: Matthew Hodgson <matthew@matrix.org>
This commit is contained in:
Travis Ralston 2022-09-12 16:32:50 -06:00 committed by GitHub
parent 42791a7f0a
commit 00aefaf09c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/client-server-api/modules/push.md
View file

@ -112,7 +112,7 @@ be marked as read. Note that users can send both an `m.read` and
If the user has both `m.read` and `m.read.private` set in the room then If the user has both `m.read` and `m.read.private` set in the room then
the receipt which is more recent/ahead must be used to determine where the receipt which is more recent/ahead must be used to determine where
the user has read up to. For example, given an ordered set of events A, the user has read up to. For example, given an oldest-first set of events A,
B, C, and D the `m.read` receipt could be at event C and `m.read.private` B, C, and D the `m.read` receipt could be at event C and `m.read.private`
at event A - the user is considered to have read up to event C. If the at event A - the user is considered to have read up to event C. If the
`m.read.private` receipt is then updated to point to B or C, the user's `m.read.private` receipt is then updated to point to B or C, the user's

4
content/client-server-api/modules/receipts.md
View file

@ -10,7 +10,7 @@ This module adds in support for receipts. These receipts are a form of
acknowledgement of an event. This module defines the `m.read` receipt acknowledgement of an event. This module defines the `m.read` receipt
for indicating that the user has read up to a given event, and `m.read.private` for indicating that the user has read up to a given event, and `m.read.private`
to achieve the same purpose without any other user being aware. Primarily, to achieve the same purpose without any other user being aware. Primarily,
`m.read.private` is meant to clear [notifications](#receiving-notifications) `m.read.private` is intended to clear [notifications](#receiving-notifications)
without advertising read-up-to status to others. without advertising read-up-to status to others.
Sending a receipt for each event can result in sending large amounts of Sending a receipt for each event can result in sending large amounts of
@ -67,7 +67,7 @@ following HTTP APIs.
{{% added-in v="1.4" %}} {{% added-in v="1.4" %}}
Some users would like to clear their [notification counts](#receiving-notifications), Some users would like to mark a room as read, clearing their [notification counts](#receiving-notifications),
but not give away the fact that they've read a particular message yet. To but not give away the fact that they've read a particular message yet. To
achieve this, clients can send `m.read.private` receipts instead of `m.read` achieve this, clients can send `m.read.private` receipts instead of `m.read`
to do exactly that: clear notifications and not broadcast the receipt to to do exactly that: clear notifications and not broadcast the receipt to