wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Clarify that clients should not ack their own messages

Browse source 
Fixes https://github.com/matrix-org/matrix-doc/issues/567
This commit is contained in:
Travis Ralston 2019-05-27 23:20:09 -06:00
parent 699cafe670
commit 4e58414b26
2 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

1
changelogs/client_server/newsfragments/2043.clarification Normal file
View file

@ -0,0 +1 @@
Clarify that clients should not send read receipts for their own messages.

4
specification/modules/receipts.rst
View file

@ -60,7 +60,8 @@ Clients should send read receipts when there is some certainty that the event in
question has been **displayed** to the user. Simply receiving an event does not question has been **displayed** to the user. Simply receiving an event does not
provide enough certainty that the user has seen the event. The user SHOULD need provide enough certainty that the user has seen the event. The user SHOULD need
to *take some action* such as viewing the room that the event was sent to or to *take some action* such as viewing the room that the event was sent to or
dismissing a notification in order for the event to count as "read". dismissing a notification in order for the event to count as "read". Clients
SHOULD NOT send read receipts for events sent by their own user.
A client can update the markers for its user by interacting with the following A client can update the markers for its user by interacting with the following
HTTP APIs. HTTP APIs.
@ -94,4 +95,3 @@ Security considerations
As receipts are sent outside the context of the event graph, there are no As receipts are sent outside the context of the event graph, there are no
integrity checks performed on the contents of ``m.receipt`` events. integrity checks performed on the contents of ``m.receipt`` events.