-
Notifications
You must be signed in to change notification settings - Fork 384
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
MSC3871: Gappy timelines #3871
base: main
Are you sure you want to change the base?
MSC3871: Gappy timelines #3871
Conversation
As suggested by @benkuly, #3871 (comment) The synthetic event approach is still listed as an alternative
d90bb0b
to
5f7bb0e
Compare
…n explanation just above
messages anyway but they do probably see our slow `/messages` pagination. | ||
|
||
|
||
### Expose `prev_events` to the client |
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.
That would simplify things dramatically, seems.
Same approach of gap-filling that is used for server-server could be employed for client-server.
Additionally, would make it possible for clients to issue full events, as wondered in MSC4080, since it becomes possible for clients to detect forward extremeties.
A proposal for letting homeservers give feedback to clients where there is a gap in the timeline from a
/messages
response.Rendered
Spawned from a discussion with @erikjohnston about making
/messages
faster