The meta category in a forum I am in was made open to everyone after initially only being accessible to TL1+. I frequent that category, meta discussion is interesting to me. My posts have gotten a good amount of likes, just enough to earn badges if it were public before.
And I have more notifications for badges than that. Earning the same badge several times notification should be collapsed into a single one and say Earned '{badge_name}' (xN) where N is the amount of times that badge was earned.
I’ve given feedback to that forum through the meta category to disable earning badges before making another category public, or silently award the badge, but merging duplicate notifications into 1 should be the ux anyway.
That’s alot of badges! Is it possible that an admin on that site lowered the number of likes required to be awarded those badges, so it is awarding them more often?
Oh, I see. The category was just made public, resulting in you being awarded for many at once. That sounds to me like a rare fluke occurrence that does not need a systematic response.
Sorry to bump an old topic, but I’m wondering if the issue here is not that the Good Reply badge was granted multiple times but that the notification for the badge was sent multiple times? This is an issue that’s come up a few times when handling support requests. It’s tricky to debug, but it seems that notifications for a badge will continue to be sent until one of the notifications is marked as read. If that is correct, does having a badge notification marked as read require the user to visit the badge’s page? That seems to be what’s happening here:
I could be totally off-base on this, but today is the second time I’ve tried to track down the cause of the issue.
@joellabes لقد نقلت موضوعك إلى هذا الموضوع للحفاظ على تجميع الطلبات معًا، حيث أعتقد أن دمجها في إشعار واحد بنفس طريقة الإعجابات/ردود الفعل حيثما أمكن سيكون أكثر أناقة أيضًا، وسيكون طريقة عملية للتأكد من عدم وجود عدة رسائل غير مقروءة تشير إلى نفس المكان.
