Ensure muted tags remain muted

Contribute Feature

AI-generated summary

hellekin reports an issue where muted tags still appear in notifications after a topic is moved between categories — for instance, from a muted to a watched category, then to another. This contradicts user expectations that muted tags should never trigger notifications. hellekin suggests implementing an “un-notification process” to remove such notifications from the queue when topics leave watched categories, or adding a delay before notifications fire to allow tag muting to take effect. The core issue is that muted tags should carry more weight than category-level notification settings. The post ends with reversed text, likely a formatting error, but the intent is clear: muted tags must remain muted even when topics move, and the system should prevent or cancel notifications triggered by such movements. This is a feature request under the notifications category, aimed at improving consistency in how muted tags behave across category transitions.

1

Situation

In some cases, muted tags can appear in notifications. In the following case, a topic was moved from a muted category to a watched category, and then to another one, overriding the muted tag (with the watched category) and creating a notification.

Continuing the discussion from Muted tag still shows in my notifications:

What should happen?

Instead, the newly created notification should be reverted to prevent the muted tag from appearing.

Why is this important?

As topics can be, and are, moved around, it happens that muted tags appear in the notifications more often than they should.

How to do it?

Tracking notifications may be impractical, but in many cases, topics moved from one category to the next can happen fast, within minutes. Maybe firing notifications on muted tags could be delayed, so that important notifications happen first, but muted notifications happen later, in a way that may prevent unnecessary fire. Muted notifications should weigh more than watched notifications. Maybe this way notification jobs can be removed before they get done, or notifications can be removed from the queue – which may create other issues, like inopportune disappearance of notifications while the user is watching the queue.

What do you think?

1 Like