|
|
|
@ -88,7 +88,7 @@ Responses:
|
|
|
|
```
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
```
|
|
|
|
GET _matrix/media/v4/media/fetch/{hash}
|
|
|
|
GET _matrix/media/v?/media/fetch/{hash}
|
|
|
|
|
|
|
|
|
|
|
|
Rate-limited: Yes
|
|
|
|
Rate-limited: Yes
|
|
|
|
Authentication: Yes
|
|
|
|
Authentication: Yes
|
|
|
|
@ -187,10 +187,11 @@ be implementation-specific, or be built-into bots like mjolnir.
|
|
|
|
|
|
|
|
|
|
|
|
## Unstable prefix
|
|
|
|
## Unstable prefix
|
|
|
|
|
|
|
|
|
|
|
|
*If a proposal is implemented before it is included in the spec, then implementers must ensure that the
|
|
|
|
This MSC uses the unstable prefix `nl.automatia.msc3468`;
|
|
|
|
implementation is compatible with the final version that lands in the spec. This generally means that
|
|
|
|
|
|
|
|
experimental implementations should use `/unstable` endpoints, and use vendor prefixes where necessary.
|
|
|
|
- `_matrix/media/nl.automatia.msc3468/clone/{serverName}/{mediaId}`
|
|
|
|
For more information, see [MSC2324](https://github.com/matrix-org/matrix-doc/pull/2324). This section
|
|
|
|
- `_matrix/media/nl.automatia.msc3468/hash/{serverName}/{mediaId}`
|
|
|
|
should be used to document things such as what endpoints and names are being used while the feature is
|
|
|
|
- `_matrix/federation/nl.automatia.msc3468/media/hash`
|
|
|
|
in development, the name of the unstable feature flag to use to detect support for the feature, or what
|
|
|
|
- `_matrix/media/nl.automatia.msc3468/media/fetch/{hash}`
|
|
|
|
migration steps are needed to switch to newer versions of the proposal.*
|
|
|
|
- `nl.automatia.msc3468.clone.mxc`
|
|
|
|
|
|
|
|
- `nl.automatia.msc3468.mxc.hash`
|
Jonathan de Jong
4 years ago