From 7af95c1f4edca5e63fd37351d499ad075ff18fb6 Mon Sep 17 00:00:00 2001 From: David Teller Date: Thu, 8 Sep 2022 17:09:08 +0200 Subject: [PATCH] WIP: Expanding policy rules to individual events --- proposals/3847-ignoring-invites-with-policy-rooms.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/proposals/3847-ignoring-invites-with-policy-rooms.md b/proposals/3847-ignoring-invites-with-policy-rooms.md index fe3a22daa..a92261d47 100644 --- a/proposals/3847-ignoring-invites-with-policy-rooms.md +++ b/proposals/3847-ignoring-invites-with-policy-rooms.md @@ -77,6 +77,14 @@ The expected behavior is that: monitor room R for new policies and apply the recommendations on behalf of Alice, interpreting such policies as "ignore invites". +### Expanding recommendations to individual events + +Policy lists define three scopes `m.policy.rule.user` for rules that deal with users, +`m.policy.rule.room` for rules that deals with rooms and `m.policy.rule.server` for +rules that deal with servers. + +We expand these lists with a fourth scope `m.policy.rule.event` for rules that deal +with individual events, in this case ignoring a specific invite. ### Suggested client behaviour @@ -154,5 +162,6 @@ In other words, using a room as source requires trusting the administrator of th During testing: - `m.ignore.invites` should be prefixed `org.matrix.msc3847.ignore.invites`; -- `m.policies` should be prefixed `org.matrix.msc3847.policies`. +- `m.policies` should be prefixed `org.matrix.msc3847.policies`; +- `m.policy.rule.event` should be prefixed `org.matrix.msc3847.policy.rule.event`.