From d197a5761fcfda0bd121f5a449673f144e8137a7 Mon Sep 17 00:00:00 2001 From: "J. Ryan Stinnett" Date: Tue, 11 Dec 2018 16:05:42 +0000 Subject: [PATCH] Clarify encrypted push rules Fix `.m.rule.encrypted_room_one_to_one` by moving a condition to the right block of the rule. Fix `.m.rule.encrypted` to state that it applies to group rooms. Signed-off-by: J. Ryan Stinnett --- specification/modules/push.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/specification/modules/push.rst b/specification/modules/push.rst index 4a6dfb10..008eaa8b 100644 --- a/specification/modules/push.rst +++ b/specification/modules/push.rst @@ -485,6 +485,11 @@ Definition: { "kind": "room_member_count", "is": "2" + }, + { + "kind": "event_match", + "key": "type", + "pattern": "m.room.encrypted" } ], "actions": [ @@ -496,11 +501,6 @@ Definition: { "set_tweak": "highlight", "value": false - }, - { - "kind": "event_match", - "key": "type", - "pattern": "m.room.encrypted" } ] } @@ -569,7 +569,7 @@ Definition: Matches all encrypted events. Unlike other push rules, this rule cannot be matched against the content of the event by nature of it being encrypted. This causes the rule to be an "all or nothing" match where it either -matches *all* events that are encrypted (in 1:1 rooms) or none. +matches *all* events that are encrypted (in group rooms) or none. Definition: