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

Batch receipts by thread as well as room #1685

Merged
merged 3 commits into from
Dec 5, 2023
Merged

Batch receipts by thread as well as room #1685

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a8cbc09
Batch receipts by thread as well as room
andybalaam Dec 1, 2023
0afb69e
Changelog for 1685
andybalaam Dec 1, 2023
61c0189
Update changelogs/client_server/newsfragments/1685.clarification
richvdh Dec 5, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelogs/client_server/newsfragments/1685.clarification
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Clarify that read-receipts should be batched by thread as well as room.
2 changes: 1 addition & 1 deletion content/client-server-api/modules/receipts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -208,7 +208,7 @@ event when the user expands that thread.

#### Server behaviour

For efficiency, receipts SHOULD be batched into one event per room
For efficiency, receipts SHOULD be batched into one event per room and thread
before delivering them to clients.

Some receipts are sent across federation as EDUs with type `m.receipt`. The
Expand Down
Loading