-
Notifications
You must be signed in to change notification settings - Fork 370
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
MSC2316: Federation queries to aid with database recovery #2316
base: old_master
Are you sure you want to change the base?
Conversation
Co-authored-by: Jason Volk <jason@zemos.net> Signed-off-by: Tulir Asokan <tulir@maunium.net> Signed-off-by: Jason Volk <jason@zemos.net>
Signed-off-by: Tulir Asokan <tulir@maunium.net>
Signed-off-by: Tulir Asokan <tulir@maunium.net>
Co-authored-by: Jason Volk <jason@zemos.net> Signed-off-by: Tulir Asokan <tulir@maunium.net> Signed-off-by: Jason Volk <jason@zemos.net>
@turt2live I don't think this is particularly WIP (or at least I hope I marked it ready for review because it was ready for review) |
value, but SHOULD NOT return more events than the specified value. | ||
|
||
> Note that if a limit is imposed, the selection for *which* member events | ||
are included in the response is implementation dependent. |
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.
Should this be changed to prefer including at least the latest join events in each room? Otherwise it would be possible for the response to only include leave events, which by my understanding would not be terribly useful since the server could then think it's not in the rooms for those events.
there was an initial implementation of this at matrix-org/synapse#6230, but it got abandoned. |
Author: @jevolk
Rendered