From d96e09593f97da9d3bad014e50849678158d86e2 Mon Sep 17 00:00:00 2001 From: Patrick Cloke Date: Mon, 6 Mar 2023 11:14:13 -0500 Subject: [PATCH] Use first-principles. --- content/client-server-api/modules/push.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/content/client-server-api/modules/push.md b/content/client-server-api/modules/push.md index 7b6b06fe..9c8d0adf 100644 --- a/content/client-server-api/modules/push.md +++ b/content/client-server-api/modules/push.md @@ -155,8 +155,12 @@ The different `kind`s of rule, in the order that they are checked, are: 1. **Content-specific rules (`content`).** These configure behaviour for (unencrypted) messages that match certain patterns. Content rules take one parameter: `pattern`, that gives the - glob pattern to match against. This is treated in the same way as - `pattern` for `event_match` against a `key` of `content.body`. + [glob-style pattern](/appendices#glob-style-matching) to match against. + The match is performed case-insensitively, and must match any substring of + the `content.body` property which starts and ends at a word boundary. A word + boundary is defined as the start or end of the value, or any character not + in the sets `[A-Z]`, `[a-z]`, `[0-9]` or `_`.The exact meaning of + "case insensitive" is defined by the implementation of the homeserver. 1. **Room-specific rules (`room`).** These rules change the behaviour of all messages for a given room. The