Suggest Modification to "Updated Topic" Count Notification

Contribute Bug

AI-generated summary

A user, mblatz, reported an issue where the “Updated Topic” count notification includes muted topics, causing confusion. codinghorror confirmed this as an annoying problem that has been reported before. sam classified it as a bug, but a challenging one to fix. Three possible solutions were proposed:

  1. Track muted topics for each user, but this approach is resource-intensive.
  2. Exclude users who muted a topic from the update, which may cause issues with large numbers of muted users.
  3. Make an additional AJAX request to double-check the data, which would increase server chatter but is considered the “least evil” option.
1

Hello. I am a Discourse user on another private forum. I noticed that even though I may have muted some topics, if those topics are updated they are still then reflected in the count displayed in the notification at top of forum that tells a user “[count] new or updated topics. Click to show”. This leads to the situation where clicking may (and often does for me and others) show nothing different that what was previously listed. Sometimes a bit confusing…

If this feature is working as intended, please disregard. If it makes sense that this count should only reflect new and un-muted topics, but not muted ones, please consider an appropriate modification.

3 « J'aime »
2

Yes, this is indeed annoying, has been reported before.

3

Il s’agit d’un Contribute > Bug, mais d’un bogue extrêmement difficile à corriger.

Option 1 :

  • L’objet utilisateur actuel garde une trace de tous les sujets que vous avez mis en sourdine, puis lors de la réception des messages, nous vérifions toujours systématiquement par rapport à cette liste (trop lourd)

Option 2 :

  • Le bus de messages exclut tous les utilisateurs qui ont mis le sujet en sourdine de la mise à jour (acceptable si seulement 10 personnes l’ont mis en sourdine, catastrophique si 10 000 personnes l’ont fait)

Option 3 :

  • Ajouter une requête AJAX supplémentaire après la réception d’une mise à jour du bus de messages qui « vérifie » les données que vous avez reçues via le bus de messages. (le moindre mal, mais augmente considérablement le trafic)

Je ne vois pas de moyen simple de corriger ce problème, il s’agit juste d’un compromis :mountain:

5 « J'aime »