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:
Track muted topics for each user, but this approach is resource-intensive.
Exclude users who muted a topic from the update, which may cause issues with large numbers of muted users.
Make an additional AJAX request to double-check the data, which would increase server chatter but is considered the “least evil” option.
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.
O objeto do usuário atual mantém o controle de todos os tópicos que você silenciou, e então, quando recebemos mensagens, sempre verificamos contra essa lista (pesado demais)
Opção 2:
O barramento de mensagens exclui todos os usuários que silenciaram o tópico da atualização (ok se apenas 10 pessoas silenciaram, um desastre se 10.000 silenciaram)
Opção 3:
Adicionar uma requisição ajax extra após recebermos uma atualização do barramento de mensagens que “verifica novamente” os dados que você recebeu do barramento de mensagens. (o menos pior, mas aumenta bastante o tráfego)
Não consigo pensar em uma maneira fácil de corrigir isso, é apenas um compromisso
