Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify that clients should not ack their own messages #2043

Merged
merged 1 commit into from May 28, 2019
Merged

Clarify that clients should not ack their own messages #2043

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions changelogs/client_server/newsfragments/2043.clarification
View file
Open in desktop
@@ -0,0 +1 @@
Clarify that clients should not send read receipts for their own messages.
4 changes: 2 additions & 2 deletions specification/modules/receipts.rst
View file
Open in desktop
Expand Up @@ -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
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
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
HTTP APIs.
Expand Down Expand Up @@ -94,4 +95,3 @@ Security considerations

As receipts are sent outside the context of the event graph, there are no
integrity checks performed on the contents of ``m.receipt`` events.