matrix.org/content/blog/2024/03/2024-03-22-matrix-v1.10-release.md

+++
title = "Matrix v1.10 release"
date = "2024-03-22T16:52:27Z"
path = "/blog/2024/03/22/matrix-v1.10-release"

[taxonomies]
author = ["Travis Ralston"]
category = ["Releases", "Spec"]
+++


Hey all,

[Matrix 1.10](https://spec.matrix.org/v1.10/) is here! We aim to release the specification once in each calendar quarter, and with Q1 wrapping up in a few days we’re due for this quarter’s release. It has been 5 months since the last release ([Matrix 1.9](https://matrix.org/blog/2023/11/29/matrix-v1.9-release/)) brought in some protocol maintenance for us though, and the implementation teams have been hard at work building the [Matrix 2.0 stack](https://matrix.org/blog/2023/09/matrix-2-0/) concurrent to the Matrix 1.10 work released today.

A total of 9 MSCs are released in Matrix 1.10, covering a wide range of maintenance, Matrix 2.0 preparation, and features for clients to use. This post focuses a bit on the Matrix 2.0 front and what’s expected in Matrix 1.11’s release cycle, but read on to the changelog at the bottom for full details on the changes which make up Matrix 1.10.


## MSC3077: Multi-stream VoIP

[MSC3077](https://github.com/matrix-org/matrix-spec-proposals/blob/main/proposals/3077-multi-stream-voip.md) and its related proposal [MSC3291](https://github.com/matrix-org/matrix-spec-proposals/blob/main/proposals/3291-muting.md) (muting in VoIP calls) lay some foundational groundwork for proper group VoIP to land in Matrix - an objective of Matrix 2.0. Currently this is taking shape at [MSC3898](https://github.com/matrix-org/matrix-spec-proposals/pull/3898) and [MSC3401](https://github.com/matrix-org/matrix-spec-proposals/pull/3401), though Element’s VoIP team is considering a possible third alternative which runs [MSC3401](https://github.com/matrix-org/matrix-spec-proposals/pull/3401) over something like LiveKit’s SFU - stay tuned for updates there. In the meantime, users in native 1:1 calls can enjoy proper screen sharing and mute capabilities ahead of the 1:N call support later this year.

As always, early review is appreciated though please note that [MSC3898](https://github.com/matrix-org/matrix-spec-proposals/pull/3898) and [MSC3401](https://github.com/matrix-org/matrix-spec-proposals/pull/3401) are particularly in flux at the moment.


## Up next in Matrix 1.11 and beyond

Over the next 2-3 months, we’ll be focusing on the following MSCs:



* Trust & Safety improvements (at the protocol level).
    * [MSC3823](https://github.com/matrix-org/matrix-spec-proposals/issues/3823) - Account suspension
    * [MSC3939](https://github.com/matrix-org/matrix-spec-proposals/issues/3939) - Account locking
    * [MSC3916](https://github.com/matrix-org/matrix-spec-proposals/issues/3916) - Authentication for media (time permitting)
    * [MSC4117](https://github.com/matrix-org/matrix-spec-proposals/issues/4117) - Reversible redactions (pre-implementation review)
    * MSCs around a “reporting v2” flow in light of various legislation and compliance requirements. These MSCs are currently being written and should be up for pre-implementation review within the Matrix 1.11 cycle.
* Early review of Matrix 2.0 features as they become ready.
    * Sliding sync ([MSC3575](https://github.com/matrix-org/matrix-spec-proposals/pull/3575)) + applicable extensions.
    * Group VoIP - Exact MSCs to be determined, as they may change following implementation.
    * OIDC Authentication - Exact MSCs to be determined.
* Pre-implementation review of [Extensible Events](https://github.com/matrix-org/matrix-spec-proposals/blob/main/proposals/1767-extensible-events.md) core content blocks MSCs.
    * Many of these MSCs require updates before they are ready for formal review.
    * [MSC3954](https://github.com/matrix-org/matrix-doc/pull/3954) - Emotes
    * [MSC3955](https://github.com/matrix-org/matrix-doc/pull/3955) - Notices / automated events
    * [MSC3927](https://github.com/matrix-org/matrix-doc/pull/3927) - Audio
    * [MSC3551](https://github.com/matrix-org/matrix-doc/pull/3551) - Files
    * [MSC3552](https://github.com/matrix-org/matrix-doc/pull/3552) - Images and Stickers
    * [MSC3553](https://github.com/matrix-org/matrix-doc/pull/3553) - Videos

Additionally, we’ll be continuing to define the expectations of a Spec Core Team member, particularly as it relates to the upcoming Governing Board for the Foundation. This exercise has been extremely valuable to us so far, and will help identify areas the Foundation and SCT may need support from each other.


## The full changelog

Read on for full details of what’s in Matrix 1.10:

### Client-Server API

**Backwards Compatible Changes**

- Allow `/versions` to optionally accept authentication, as per [MSC4026](https://github.com/matrix-org/matrix-spec-proposals/pull/4026). ([#1728](https://github.com/matrix-org/matrix-spec/issues/1728))
- Add local erasure requests, as per [MSC4025](https://github.com/matrix-org/matrix-spec-proposals/pull/4025). ([#1730](https://github.com/matrix-org/matrix-spec/issues/1730))
- Use the `body` field as optional media caption, as per [MSC2530](https://github.com/matrix-org/matrix-spec-proposals/pull/2530). ([#1731](https://github.com/matrix-org/matrix-spec/issues/1731))
- Add server support discovery endpoint, as per [MSC1929](https://github.com/matrix-org/matrix-spec-proposals/pull/1929). ([#1733](https://github.com/matrix-org/matrix-spec/issues/1733))
- Add support for multi-stream VoIP, as per [MSC3077](https://github.com/matrix-org/matrix-spec-proposals/pull/3077). ([#1735](https://github.com/matrix-org/matrix-spec/issues/1735))
- Specify that the `Retry-After` header may be used to rate-limit a client, as per [MSC4041](https://github.com/matrix-org/matrix-spec-proposals/pull/4041). ([#1737](https://github.com/matrix-org/matrix-spec/issues/1737))
- Add support for recursion on the `GET /relations` endpoints, as per [MSC3981](https://github.com/matrix-org/matrix-spec-proposals/pull/3981). ([#1746](https://github.com/matrix-org/matrix-spec/issues/1746))

**Spec Clarifications**

- The [strike](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/strike) element is deprecated in the HTML spec. Clients should prefer [s](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/s) instead. ([#1629](https://github.com/matrix-org/matrix-spec/issues/1629))
- Clarify that read receipts should be batched by thread as well as by room. ([#1685](https://github.com/matrix-org/matrix-spec/issues/1685))
- Clarify that threads can be created based on replies. ([#1687](https://github.com/matrix-org/matrix-spec/issues/1687))
- Clarify in the reply fallbacks example that the prefix sequence should be repeated for each line. ([#1690](https://github.com/matrix-org/matrix-spec/issues/1690))
- Clarify the format of account data objects for secret storage. ([#1695](https://github.com/matrix-org/matrix-spec/issues/1695), [#1734](https://github.com/matrix-org/matrix-spec/issues/1734))
- Clarify that the key backup MAC is implemented incorrectly and does not pass the ciphertext through HMAC-SHA-256. ([#1712](https://github.com/matrix-org/matrix-spec/issues/1712))
- Clarify one-time key and fallback key types in examples. ([#1715](https://github.com/matrix-org/matrix-spec/issues/1715))
- Clarify that the HKDF calculation for SAS uses base64-encoded keys rather than the raw key bytes. ([#1719](https://github.com/matrix-org/matrix-spec/issues/1719))
- Clarify how to perform the ECDH exchange in step 12 of the SAS process. ([#1720](https://github.com/matrix-org/matrix-spec/issues/1720))
- Document the deprecation policy of HTML tags, as per [MSC4077](https://github.com/matrix-org/matrix-spec-proposals/pull/4077). ([#1732](https://github.com/matrix-org/matrix-spec/issues/1732))
- The [font](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/font) element is deprecated in the HTML spec. Clients should prefer [span](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/span) with the `data-mx-bg-color` and `data-mx-color` attributes instead. ([#1739](https://github.com/matrix-org/matrix-spec/issues/1739))
- Disambiguate uses of `PublicRoomsChunk` in the `GET /hierarchy` endpoint. ([#1740](https://github.com/matrix-org/matrix-spec/issues/1740))
- Clarify that `sdpMid` and `sdpMLineIndex` are not required in `m.call.candidates`. ([#1742](https://github.com/matrix-org/matrix-spec/issues/1742))
- Fix various typos throughout the specification. ([#1748](https://github.com/matrix-org/matrix-spec/issues/1748))
- Clearly indicate that each `Content-Type` may have distinct behaviour on non-JSON requests/responses. ([#1756](https://github.com/matrix-org/matrix-spec/issues/1756))
- Clarify that the `m.push_rules` account data type cannot be set using the `/account_data` API, as per [MSC4010](https://github.com/matrix-org/matrix-spec-proposals/pull/4010). ([#1763](https://github.com/matrix-org/matrix-spec/issues/1763))


### Server-Server API

**Spec Clarifications**

- Clarify Server-Server API request signing example by using the `POST` HTTP method, as `GET` requests don't have request bodies. ([#1721](https://github.com/matrix-org/matrix-spec/issues/1721))
- Disambiguate uses of `PublicRoomsChunk` in the `GET /hierarchy` endpoint. ([#1740](https://github.com/matrix-org/matrix-spec/issues/1740))
- Clarify that the `children_state`, `room_type` and `allowed_room_ids` properties in the items of the `children` array of the response of the `GET /hierarchy` endpoint are not required. ([#1741](https://github.com/matrix-org/matrix-spec/issues/1741))


### Application Service API

**Spec Clarifications**

- Clarify that the `/login` and `/register` endpoints should fail when using the `m.login.application_service` login type without a valid `as_token`. ([#1744](https://github.com/matrix-org/matrix-spec/issues/1744))


### Identity Service API

No significant changes.


### Push Gateway API

No significant changes.


### Room Versions

**Spec Clarifications**

- For room versions 7 through 11: Clarify that `invite->knock` is not a legal transition. ([#1717](https://github.com/matrix-org/matrix-spec/issues/1717))


### Appendices

No significant changes.


### Internal Changes/Tooling

**Spec Clarifications**

- Update the spec release process. ([#1680](https://github.com/matrix-org/matrix-spec/issues/1680))
- Minor clarifications to the contributing guide. ([#1697](https://github.com/matrix-org/matrix-spec/issues/1697))
- Update Docsy to v0.8.0. ([#1699](https://github.com/matrix-org/matrix-spec/issues/1699), [#1762](https://github.com/matrix-org/matrix-spec/issues/1762))
- Fix npm release script for `@matrix-org/spec`. ([#1713](https://github.com/matrix-org/matrix-spec/issues/1713))
- Add some clarifications around implementation requirements for MSCs. ([#1718](https://github.com/matrix-org/matrix-spec/issues/1718))
- Update HTML templates to include links to object schema definitions. ([#1724](https://github.com/matrix-org/matrix-spec/issues/1724))
- Factor out all the common parameters of the various `/relations` apis. ([#1745](https://github.com/matrix-org/matrix-spec/issues/1745))
- Add support for `$ref` URIs containing fragments in OpenAPI definitions and JSON schemas. ([#1751](https://github.com/matrix-org/matrix-spec/issues/1751), [#1754](https://github.com/matrix-org/matrix-spec/issues/1754))