Skip to content

MSC4000: Forwards fill (/backfill forwards) #4000

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

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

MSC4000: Forwards fill (/backfill forwards) #4000

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e592875
Add initial proposal for forwards fill
MadLittleMods Apr 14, 2023
1cdfd0b
Use MSC number
MadLittleMods Apr 14, 2023
c3bba84
Determine support by optimistically trying and looking at error response
MadLittleMods Apr 17, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Determine support by optimistically trying and looking at error response 
See #4000 (comment)
  • Loading branch information
@MadLittleMods
MadLittleMods committed Apr 17, 2023
commit c3bba8447ea7cd17654a9bd89a7eecf93e9164f9
30 changes: 16 additions & 14 deletions proposals/4000-forwards-fill.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,26 +123,28 @@ stable `/v1` location as described above.

### While the MSC is unstable

During this period, to detect server support, other servers should check for the
presence of the `org.matrix.msc4000` flag in `unstable_features` on `/versions`. Servers
are also required to use the unstable prefixes (see [unstable prefix](#unstable-prefix))
during this time.
During this period, servers should optimistically try the unstable endpoint and look for
the `404` `M_UNRECOGNIZED` error code to determine support (see [MSC3743: *Standardized
error response for unknown
endpoints*](https://github.com/matrix-org/matrix-spec-proposals/pull/3743)).

### Once the MSC is merged but not in a spec version

Once this MSC is merged, but is not yet part of the spec, servers should rely on the
presence of the `org.matrix.msc4000.stable` flag in `unstable_features` to determine
server support. If the flag is present, servers are required to use stable prefixes (see
[unstable prefix](#unstable-prefix)).
Once this MSC is merged, but is not yet part of the spec, servers should optimistically
use the stable endpoint and fallback to the unstable endpoint to have maximum
compatibility if desired.

### Once the MSC is in a spec version

Once this MSC becomes a part of a spec version, servers should rely on the presence of
the spec version, that supports the MSC, in `versions` on `/versions`, to determine
support. Servers are encouraged to keep the `org.matrix.msc4000.stable` flag around for
a reasonable amount of time to help smooth over the transition for other servers.
"Reasonable" is intentionally left as an implementation detail, however the MSC process
currently recommends *at most* 2 months from the date of spec release.
Once this MSC becomes a part of a spec version, servers should optimistically use the
stable endpoint. If a given server doesn't support the endpoint, another server in the
room can be tried until all are exhausted.

Servers can keep falling back to the unstable endpoint and are encouraged (not
obligated) to serve the unstable fallback endpoint for a reasonable amount of time to
help smooth over the transition for other servers. "Reasonable" is intentionally left as
an implementation detail, however the MSC process currently recommends *at most* 2
months from the date of spec release.