You're looking at an unstable version of this specification. Unstable specifications may change at any time without notice.
Changes since last release
| Git commit | https://github.com/matrix-org/matrix-spec/tree/b1fd2af |
|---|---|
| Checklist | checklist.md |
Client-Server API
Removed Endpoints
Backwards Compatible Changes
- Allow application services to masquerade as specific devices belonging to users, as per MSC4326. (#2221)
- Add the
m.oauthauthentication type for User-Interactive Authentication as per MSC4312. (#2234)
Spec Clarifications
- Push rule IDs are globally unique within their kind. (#2214)
- Don’t advertise
creatorfield in description of room creation. (#2215) room_idis required for peeking via/_matrix/client/v3/events. (#2216)- The
server-namesegment of MXC URIs is sanitised differently from themedia-idsegment. (#2217) - Add note to each endpoint that uses capability negotiation. (#2223)
- Fix various typos throughout the specification. (#2224, #2227)
- Additional OpenGraph properties can be present in URL previews. (#2225)
- Clarify the special casing of membership events and redactions in power levels. (#2231)
M_RESOURCE_LIMIT_EXCEEDEDis now listed as a common error code. (#2232)- Add
m.login.termsto enumeration of authentication types. (#2233) - Clarify how to use
state_afterahead of declaring full support for its spec version. (#2240) device_one_time_keys_countis only optional if no unclaimed one-time keys exist. (#2245)- Clarify that servers may choose not to use
M_USER_DEACTIVATEDat login time, for example for privacy reasons when they can’t authenticate deactivated users. (#2246) - Minor grammatical fix in the Secrets module description. (#2250)
Server-Server API
No significant changes.
Application Service API
Backwards Compatible Changes
- Allow application services to masquerade as specific devices belonging to users, as per MSC4326. (#2221)
Spec Clarifications
- Fix JSON formatting in the “Server admin style permissions” examples. (#2213)
Identity Service API
No significant changes.
Push Gateway API
No significant changes.
Room Versions
Spec Clarifications
- In room versions 8 through 12, clarify that “sufficient permission to invite users” on restricted joins also includes being a joined member of the room. (#2220)
- In room versions 3 through 12, clarify that when you have the power to redact, it is possible to redact events that you don’t have the power to send. (#2249)
Appendices
No significant changes.
Internal Changes/Tooling
Spec Clarifications