# "X new / updated topics" gets triggered for muted topics

**URL:** https://meta.discourse.org/t/x-new-updated-topics-gets-triggered-for-muted-topics/36226
**Category:** Bug
**Tags:** planned
**Created:** [2 בדצמבר,‏ 2015,‏ 2:51am UTC](https://meta.discourse.org/t/x-new-updated-topics-gets-triggered-for-muted-topics/36226 "2015-12-02T02:51:19Z")
**Posts on this page:** 1
**Showing post:** 14

<div class="post-metadata">

### Author: ![ChrisBeach](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chrisbeach/32/214628_2.png) [@ChrisBeach](https://meta.discourse.org/u/ChrisBeach)
#### Post date: [16 באוגוסט,‏ 2017,‏ 8:45am UTC](https://meta.discourse.org/t/x-new-updated-topics-gets-triggered-for-muted-topics/36226/14 "2017-08-16T08:45:25Z")

</div>

Our users are picking up on this issue too.

An uneducated suggestion - If update messages contain topic ids, could these be filtered on client-side based on a user’s mute list? Caching the mute-list client-side would probably be okay as I expect most users probably only mute a small handful of topics (and in any case, we’d use a bounded cache of, say, 1000 most-recently-muted topic ids). No changes to message bus infrastructure required - it would be downstream of that.

---

_[View the full topic](https://meta.discourse.org/t/x-new-updated-topics-gets-triggered-for-muted-topics/36226)._