Badge Count Anomaly
Badge count anomaly: #(2nd Anniversary) > #(1st Anniversary)
It would be total hyperbole to say it’s driving me crazy, but I’ve been so conditioned to pick up on and resolve anomalous data that I also cant unsee it. I keep zeroing in on this every time I check out a new badge to see if it’s been fixed. Besides, I’m a bit curious about the actual tvalue of #(1st Anniversary). (It would not be hyperbole to say those badge count statistics are included for people like me..)
🙃
It’s probably a longshot, but I thought I’d query the forum. Anyone else notice this? Just knowing the source of the error would probably let me out of my Pavlovian mental hangup.
🙄
@suzushka I wasn't around back then, but I think the sequence was more like:
- AHQ opens in 2012; no one bothers with badges (or maybe they did, but those badges are long gone).
 - The first badges, at least among the ones we can still see, are rolled out in September 2015. This includes "newbie" and some post and XP badges.
 - In 2017, someone decides that anniversary badges would be fun, and they start rolling out.
 - So many people are supposed to receive the first anniversary badge that things break.
 - The issue gets fixed before the other anniversary badges are released, so everyone who's earned one of those gets it.
 - Possibly: it's arranged so that people who should have received the first anniversary on the first go around will get it the next time they login, but of course they don't all come back, leaving the discrepancy in numbers that you noticed.
 
As far as I know, there aren't any other badges like this. It's possible the lesson was learned after the one rollout went badly, and everything else has worked as intended.
And I also believe that none of the anniversary badges are earned unless someone logs in again, so a user coming back after a few years would get all their anniversary badges at once. Therefore, the only people who would have the second anniversary badge and not the first one are those who were around when the rollout went badly but haven't been back since the issue was fixed.