Implement Matrix 1.10 changes

[zecakeh]

Here is the Matrix 1.10 changelog to follow our progress.

To be sure we don't miss anything, ALL entries of the changelog (except the section about internal changes) should appear here in the same order and category. The ones that we have to implement should be linked to an issue and/or a PR or commit in this repository. If an extra step is necessary when the version is released (like moving it from an unstable feature flag), a subtask should be created. The ones that don't impact us should be struck. The "contributed by"s should be removed to avoid pinging users.

1.1 Client-Server API

Backwards Compatible Changes

• Allow /versions to optionally accept authentication, as per MSC4026. (#1728) client-api: Allow /versions to optionally accept authentication #1742
• Add local erasure requests, as per MSC4025. (#1730) client-api: Add support for local user erasure #1737
• Use the body field as media caption, as per MSC2530. (#1731) Add filename and formatted fields to media messages #1732
• Add server support discovery endpoint, as per MSC1929. (#1733) client-api: Add server support discovery endpoint  #1751
• Add support for multi-stream VoIP, as per MSC3077. (#1735) events: Add support for multi-stream VoIP #1752
• Specify that the Retry-After header may be used to rate-limit a client, as per MSC4041. (#1737) client-api: Add support for the Retry-After header #1757
• Add support for recursion on the GET /relations endpoints, as per MSC3981. (#1746) client-api: Add support for recursion on the get_relating_events endpoints #1754

Spec Clarifications

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

1.2 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)
• Disambiguate uses of PublicRoomsChunk in the GET /hierarchy endpoint. (#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)

1.3 Application Service API

• Clarify that the /login and /register endpoints should fail when using the m.login.application_service login type without a valid as_token. (#1744)

1.4 Identity Service API

No significant changes.

1.5 Push Gateway API

No significant changes.

1.6 Room Versions

Spec Clarifications

• For room versions 7 through 11: Clarify that invite->knock is not a legal transition. (#1717) Disallow invite->knock membership transition  #1734

1.7 Appendices

No significant changes.

[zecakeh]

This is all done.