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.

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

Open
wants to merge 19 commits into
base: main
Choose a base branch
from
Open

Conversation

MadLittleMods
Copy link
Contributor

@MadLittleMods MadLittleMods commented Aug 18, 2022

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

@MadLittleMods MadLittleMods changed the title MSCXXX: Gappy timelines MSC3871: Gappy timelines Aug 18, 2022
@MadLittleMods MadLittleMods marked this pull request as ready for review August 18, 2022 02:39
@turt2live turt2live added proposal A matrix spec change proposal client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. labels Aug 18, 2022
proposals/3871-gappy-timelines.md Outdated Show resolved Hide resolved
proposals/3871-gappy-timelines.md Show resolved Hide resolved
proposals/3871-gappy-timelines.md Outdated Show resolved Hide resolved
As suggested by @benkuly,
#3871 (comment)

The synthetic event approach is still listed as an alternative
@MadLittleMods MadLittleMods force-pushed the madlittlemods/gappy-timelines branch from d90bb0b to 5f7bb0e Compare October 7, 2022 21:46
messages anyway but they do probably see our slow `/messages` pagination.


### Expose `prev_events` to the client

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants