Matrix: notification rules are ignored - everything or nothing #98

Closed
opened 2026-09-02 23:25:39 -04:00 by Salastil · 1 comment
Owner

No push rules anywhere (grep -rn push_rules nobilis/src is empty). Matrix keeps per-account rules on the server: keywords, per-room overrides, mentions-only, mute. Element edits them; moho neither reads nor writes them, so a room muted on your phone still alerts here and a keyword you set there is unknown.

Done looks like: /pushrules is read at connect and applied to what notifies, and per-room mute/mentions-only writes back.

No push rules anywhere (`grep -rn push_rules nobilis/src` is empty). Matrix keeps per-account rules on the server: keywords, per-room overrides, mentions-only, mute. Element edits them; moho neither reads nor writes them, so a room muted on your phone still alerts here and a keyword you set there is unknown. **Done looks like:** `/pushrules` is read at connect and applied to what notifies, and per-room mute/mentions-only writes back.
Salastil added the bug label 2026-09-03 13:11:31 -04:00
Author
Owner

Finished — and the scale of it was worse than the issue said.

Your account has eleven rooms muted through push rules set on another client, including both of the rooms moho shows. This client read none of them, so it has been announcing messages in rooms you silenced.

Rules are read at connect and two questions asked of them, because two are what people actually set: is this room muted, and does the message contain a keyword. The rest of the rule language belongs to the server. A mute goes on the buffer rather than into one message's answer, so it also silences the nick match moho makes on its own — otherwise a muted room would still light up on your name.

Writing back too: muting a Matrix room in the conversation menu now writes the push rule, so it is muted on your phone as well. Verified live against poa.st — the rule appeared with the empty action list the current spec uses, and unmuting removed it. Your eleven existing rules are untouched.

nobilis 1bd675c, moho https://git.salastil.com/Salastil/moho/commit/7786f73

Finished — and the scale of it was worse than the issue said. Your account has **eleven rooms muted** through push rules set on another client, *including both of the rooms moho shows*. This client read none of them, so it has been announcing messages in rooms you silenced. Rules are read at connect and two questions asked of them, because two are what people actually set: is this room muted, and does the message contain a keyword. The rest of the rule language belongs to the server. A mute goes on the buffer rather than into one message's answer, so it also silences the nick match moho makes on its own — otherwise a muted room would still light up on your name. Writing back too: muting a Matrix room in the conversation menu now writes the push rule, so it is muted on your phone as well. Verified live against poa.st — the rule appeared with the empty action list the current spec uses, and unmuting removed it. Your eleven existing rules are untouched. nobilis 1bd675c, moho https://git.salastil.com/Salastil/moho/commit/7786f73
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Salastil/moho#98