Add a .m.rule.tombstone default push rule for room upgrades

As per [MSC1930](https://github.com/matrix-org/matrix-doc/pull/1930)

There are no known changes to this proposal since it was accepted.
This commit is contained in:
Travis Ralston 2019-05-24 17:14:23 -06:00
parent 415212c3a0
commit ceaccffdf7
2 changed files with 34 additions and 2 deletions

View file

@ -0,0 +1 @@
Add a ``.m.rule.tombstone`` default push rule for room ugprade notifications.

View file

@ -177,7 +177,7 @@ notification is delivered for a matching event. The following actions are define
This prevents each matching event from generating a notification This prevents each matching event from generating a notification
``coalesce`` ``coalesce``
This enables notifications for matching events but activates homeserver This enables notifications for matching events but activates homeserver
specific behaviour to intelligently coalesce multiple events into a single specific behaviour to intelligently coalesce multiple events into a single
notification. Not all homeservers may support this. Those that do not support notification. Not all homeservers may support this. Those that do not support
it should treat it as the ``notify`` action. it should treat it as the ``notify`` action.
``set_tweak`` ``set_tweak``
@ -369,6 +369,37 @@ Definition:
} }
``.m.rule.tombstone``
`````````````````````
Matches any event whose type is ``m.room.tombstone``. This is intended
to notify users of a room when it is upgraded, similar to what an
``@room`` notification would accomplish.
Definition:
.. code:: json
{
"rule_id": ".m.rule.tombstone",
"default": true,
"enabled": true,
"conditions": [
{
"kind": "event_match",
"key": "type",
"pattern": "m.room.tombstone"
}
],
"actions": [
"notify",
{
"set_tweak": "highlight",
"value": true
}
]
}
``.m.rule.roomnotif`` ``.m.rule.roomnotif``
````````````````````` `````````````````````
Matches any message whose content is unencrypted and contains the Matches any message whose content is unencrypted and contains the
@ -599,7 +630,7 @@ Definition:
Conditions Conditions
++++++++++ ++++++++++
Override, Underride and Default Rules MAY have a list of 'conditions'. Override, Underride and Default Rules MAY have a list of 'conditions'.
All conditions must hold true for an event in order to apply the ``action`` for All conditions must hold true for an event in order to apply the ``action`` for
the event. A rule with no conditions always matches. Room, Sender, User and the event. A rule with no conditions always matches. Room, Sender, User and
Content rules do not have conditions in the same way, but instead have Content rules do not have conditions in the same way, but instead have