Clarify that dont_notify and coalesce MUST be gracefully ignored

Signed-off-by: Johannes Marbach <n0-0ne+github@mailbox.org>
This commit is contained in:
Johannes Marbach 2024-06-25 14:59:08 +02:00
parent 9f2891d95c
commit c616c46f53

View file

@ -184,11 +184,13 @@ they are represented as a dictionary with a key equal to their name and
other keys as their parameters, e.g. other keys as their parameters, e.g.
`{ "set_tweak": "sound", "value": "default" }`. `{ "set_tweak": "sound", "value": "default" }`.
{{% boxes/note %}} ###### Historical Actions
Older versions of the Matrix specification included the `dont_notify` and Older versions of the Matrix specification included the `dont_notify` and
`coalesce` actions. These should both be considered no-ops (ignored, not `coalesce` actions. Homeservers MUST ignore these actions by stripping them
rejected) if received from a client. from any actions array they encounter. This means that setting the actions
{{% /boxes/note %}} on a rule to e.g. `["dont_notify"]` MUST be equivalent to setting an empty
actions array.
##### Conditions ##### Conditions