|
|
|
|
@ -1,4 +1,4 @@
|
|
|
|
|
# MSC0000: Add timestamp massaging to `/join` and `/knock`
|
|
|
|
|
# MSC3998: Add timestamp massaging to `/join` and `/knock`
|
|
|
|
|
|
|
|
|
|
As mentioned in the original
|
|
|
|
|
[MSC3316](https://github.com/matrix-org/matrix-spec-proposals/pull/3316) for timestamp
|
|
|
|
|
@ -72,19 +72,19 @@ does not create any new security considerations.
|
|
|
|
|
## Unstable prefix
|
|
|
|
|
|
|
|
|
|
While this feature is in development, the `ts` querystring parameter can be used as
|
|
|
|
|
`org.matrix.mscXXXX.ts`
|
|
|
|
|
`org.matrix.msc3998.ts`
|
|
|
|
|
|
|
|
|
|
### While the MSC is unstable
|
|
|
|
|
|
|
|
|
|
During this period, to detect server support clients should check for the presence of
|
|
|
|
|
the `org.matrix.mscXXXX` flag in `unstable_features` on `/versions`. Clients are also
|
|
|
|
|
the `org.matrix.msc3998` flag in `unstable_features` on `/versions`. Clients are also
|
|
|
|
|
required to use the unstable prefixes (see [unstable prefix](#unstable-prefix)) during
|
|
|
|
|
this time.
|
|
|
|
|
|
|
|
|
|
### Once the MSC is merged but not in a spec version
|
|
|
|
|
|
|
|
|
|
Once this MSC is merged, but is not yet part of the spec, clients should rely on the
|
|
|
|
|
presence of the `org.matrix.mscXXXX.stable` flag in `unstable_features` to determine
|
|
|
|
|
presence of the `org.matrix.msc3998.stable` flag in `unstable_features` to determine
|
|
|
|
|
server support. If the flag is present, clients are required to use stable prefixes (see
|
|
|
|
|
[unstable prefix](#unstable-prefix)).
|
|
|
|
|
|
|
|
|
|
@ -92,7 +92,7 @@ server support. If the flag is present, clients are required to use stable prefi
|
|
|
|
|
|
|
|
|
|
Once this MSC becomes a part of a spec version, clients 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.mscXXXX.stable` flag around for
|
|
|
|
|
support. Servers are encouraged to keep the `org.matrix.msc3998.stable` flag around for
|
|
|
|
|
a reasonable amount of time to help smooth over the transition for clients. "Reasonable"
|
|
|
|
|
is intentionally left as an implementation detail, however the MSC process currently
|
|
|
|
|
recommends *at most* 2 months from the date of spec release.
|
Eric Eastwood
1 year ago