-
-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify that dont_notify and coalesce MUST be gracefully ignored #1890
Clarify that dont_notify and coalesce MUST be gracefully ignored #1890
Conversation
Signed-off-by: Johannes Marbach <n0-0ne+github@mailbox.org>
I did check the original MSC and that uses (lowercase) "should" and "recommended", but I really think it is a requirement for backwards compatibility. |
`coalesce` actions. Homeservers MUST ignore these actions by stripping them | ||
from any actions array they encounter. This means that setting the actions | ||
on a rule to e.g. `["dont_notify"]` MUST be equivalent to setting an empty | ||
actions array. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not that I'm keen on making this more complicated but I'm now wondering if this clause should apply to clients as well since they might receive default push rules with dont_notify
when connecting to an older server? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it probably also applies to clients working with an old server.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I have rephrased the paragraph slightly to include clients as well.
Relates to: https://github.com/matrix-org/matrix-spec/pull/1501/files#r1176822971.
I replaced the info box with a subsection akin to the one for historical user IDs to prevent using RFC2119 keywords inside an explanatory box.
I also attempted to be a little more verbose about what ignoring means by describing the filtering behavior implemented in Synapse.
CC @clokep
Pull Request Checklist
Preview: https://pr1890--matrix-spec-previews.netlify.app