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

Consider moving unread_notifications into summary in /sync #476

Open
turt2live opened this issue May 28, 2019 · 0 comments
Open

Consider moving unread_notifications into summary in /sync #476

turt2live opened this issue May 28, 2019 · 0 comments
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol

Comments

@turt2live
Copy link
Member

From MSC688

We add a new section to the /sync response for a given room called ‘summary’. This is similar to the ‘unread_notifications’ section; it’s used for updating the client whenever the aggregate information calculated about the room changes. (In fact, should we move unread_notifications into this summary section?)
@turt2live turt2live added enhancement A suggestion for a relatively simple improvement to the protocol A-Client-Server Issues affecting the CS API labels May 28, 2019
@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@turt2live