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

Include guidelines how to backfill with /messages and /context #1281

Open
MadLittleMods opened this issue Oct 12, 2022 · 0 comments
Open

Include guidelines how to backfill with /messages and /context #1281

MadLittleMods opened this issue Oct 12, 2022 · 0 comments
Labels
A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit

Comments

@MadLittleMods
Copy link
Contributor

MadLittleMods commented Oct 12, 2022

Link to problem area:

https://spec.matrix.org/v1.1/server-server-api/#backfilling-and-retrieving-missing-events

Issue

As brought up in matrix-org/complement#492 (review) and matrix-org/matrix-spec-proposals#3030 (comment), there is no right answer for when and how to backfill events.

The spec just says this:

Since users in that room are able to request the history by the /messages client API endpoint, it’s possible that they might step backwards far enough into history before the homeserver itself was a member of that room.

To cover this case, the federation API provides a server-to-server analog of the /messages client API, allowing one homeserver to fetch history from another. This is the /backfill API.

-- https://spec.matrix.org/v1.1/server-server-api/#backfilling-and-retrieving-missing-events

But it should probably also mention that /context should backfill at the very least. And have some heuristics for when exactly to backfill. Is it acceptable to have gaps (MSC3871)? etc

@MadLittleMods MadLittleMods added the clarification An area where the expected behaviour is understood, but the spec could do with being more explicit label Oct 12, 2022
@turt2live turt2live added the A-S2S Server-to-Server API (federation) label Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
Projects
None yet
Development

No branches or pull requests

2 participants