Matrix spec updates meta issue #880
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#880
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Matrix specification gets updated every 6 months or so, introducing new features and clarifications. This issue is to be used to track the status of things from the spec that we might not have implemented according to the updates yet.
As of our fork point, we already advertise support for spec versions 1.1 through 1.5. The 1.11 support was added purely so that clients would use authenticated media, not because the requirements were met. For the sake of not hanging on to versions that frankly aren't used anymore, only 1.6 and above will be tracked here.
Only things that require changes to the server itself are included. Docs changes and client changes are omitted entirely.
v1.15
client-to-server
GET /_matrix/client/v1/room_summary/{roomIdOrAlias}
, as per MSC3266. (See: #881)GET /_matrix/client/v1/auth_metadata
, as per MSC2965. (See: #810)server-to-server
/_matrix/federation/v1/hierarchy/{roomId}
with the new optional properties encryption and room_version as per MSC3266. (See: #881)v1.14
client-to-server
POST /_matrix/client/v3/users/{userId}/report
, as per MSC4260. (See: #882)v1.13
client-to-server
POST /_matrix/client/v3/rooms/{roomId}/report
, as per MSC4151.M_USER_SUSPENDED
error code behaviour, as per MSC3823.server-to-server
Appservice API
v1.12
client-to-server
POST /_matrix/client/v3/join/{roomIdOrAlias}
andPOST /_matrix/client/v3/knock/{roomIdOrAlias}
, as per MSC4156.!admin users deactivate -n
achieves the same effect. Locking is also yet to be used in the wild)v1.11
client-to-server
new endpoints
GET /_matrix/client/v1/media/config
GET /_matrix/client/v1/media/download/{serverName}/{mediaId}
GET /_matrix/client/v1/media/download/{serverName}/{mediaId}/{fileName}
GET /_matrix/client/v1/media/preview_url
GET /_matrix/client/v1/media/thumbnail/{serverName}/{mediaId}
changes
GET /thumbnail
, as per MSC2705unsigned.membership
property to events, as per MSC4115.v1.10
client-to-server
/versions
to optionally accept authentication, as per MSC4026.v1.9
did anything even change in this version lmao
client-to-server
m.rule.suppress_edits
default push rule, as per MSC3958.v1.8
client-to-server
server-to-server
matrix
SRV lookup steps during server discovery, as per MSC4040.matrix-fed
SRV lookup steps to server discovery, as per MSC4040.v1.7
client-to-server
New endpoints
POST /_matrix/media/v1/create
PUT /_matrix/media/v3/upload/{serverName}/{mediaId}
POST /_matrix/client/v1/login/get_token
Changes
m.replace
(edit) events, as per MSC3925. (See: #847)event_property_is
andevent_property_contains
, as per MSC3758 and MSC3966.Appservice API
POST /_matrix/app/v1/ping
,POST /_matrix/client/v1/appservice/{appserviceId}/ping
)v1.6
client-to-server
/rooms/<roomID>/timestamp_to_event
endpoint, as per MSC3030.server-to-server
keyId
from the server/keys
endpoints, as per MSC3938./timestamp_to_event/<roomID>
endpoint, as per MSC3030./_matrix/federation/v2/send_join
to allow omitting membership events, per MSC3706.