-
Notifications
You must be signed in to change notification settings - Fork 399
Document how read receipts work over federation #1484
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.
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
Document how read receipts work over federation #1484
Conversation
Federation format: https://github.com/matrix-org/synapse/blob/d69decd5c78c72abef50b597a689e2bc55a39702/synapse/handlers/receipts.py#L153-L166 Population of the fields that the above uses to construct the EDU: https://github.com/matrix-org/synapse/blob/d69decd5c78c72abef50b597a689e2bc55a39702/synapse/handlers/receipts.py#L48-L56
aa60209
to
e03bfbc
Compare
type: array | ||
description: |- | ||
The event ID that the user has read up to. Must be exactly | ||
one element in length. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really, no. Its the set of extremities that the user has read up to. (I think synapse cheats and mostly does only one entry). This is to support e.g. expressing you have read both sides of a fork.
specification/server_server_api.rst
Outdated
-------- | ||
|
||
Receipts are EDUs used to communicate a marker for a given event. Currently the | ||
only kind of receipt supported is a "read receipt", or where in the timeline a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The timeline isn't a thing as far as federation is concerned, really.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is to try and relate the server-server spec to the client-server things. Suggestions on improved wording would be appreciated.
@erikjohnston please take another look |
Rendered: see 'docs' commit status.
This PR is blocked on #1463 as it makes use of the "definitions embedded in the spec" feature, and builds upon EDUs.
Blocked on:
Federation format: https://github.com/matrix-org/synapse/blob/d69decd5c78c72abef50b597a689e2bc55a39702/synapse/handlers/receipts.py#L153-L166
Population of the fields that the above uses to construct the EDU: https://github.com/matrix-org/synapse/blob/d69decd5c78c72abef50b597a689e2bc55a39702/synapse/handlers/receipts.py#L48-L56