Open
Description
This issue was originally created by @S7evinK at matrix-org/dendrite#3225.
Client-Server API
Backwards Compatible Changes
- Changes to the server-side aggregation of
m.replace
(edit) events, as per MSC3925.- No event aggregation at all atm
- Add new push rule conditions
event_property_is
andevent_property_contains
, as per MSC3758 and MSC3966. - Add
m.annotation
relations (reactions), as per MSC2677.- (No aggregation?)
- Support asynchronous media uploads, as per MSC2246.
- Document the
m.mentions
property; the.m.rule.is_user_mention
and.m.rule.is_room_mention
push rules; and other notification behaviour, as per MSC3952. - Update the scope of transaction IDs, as per MSC3970.
- Add an ability to redirect media downloads, as per MSC3860.
- Add an ability to use an existing session to log in another, as per MSC3882.
Spec Clarifications
- Clarify the sections of the specification concerning aggregation of child events. (#1424)
- No event aggregation at all atm
- Clarify that servers should enforce a default
limit
on a filter if one is not specified. (#1463)- While I think we do, we should probably verify this
- Disambiguate using property names with dots in them during push rule processing, as per MSC3873 and MSC3980.
- Remove outdated text saying that
state_default
is 0 if there is nom.room.power_levels
event in a room. (#1479)- Worth validating
- Remove fictitious
token
parameter on/keys/query
endpoint. (#1485) - Remove the
dont_notify
andcoalesce
push rule actions, as per MSC3987.
Application Service API
Backwards Compatible Changes
- Add homeserver->appservice ping mechanism, as per MSC2659.
Identity Service API
Spec Clarifications
- Corrections to the response format of
/_matrix/identity/v2/store-invite
. (#1486)