Unfortunately I have recently received some upvotes, which means that new bugz are uncovered...

TL;DR: if there's a day, on which you receive upvotes on post, then you check reputation tab and after some time receive upvotes on the same post again, rep tab tells you wrong amount of new rep gain (ONLY in the "time" mode)

Reputation tab shows everything correctly if there aren't any new reputation changes since the last time you have visited the rep tab. Otherwise, there could be problems.

I'll give you a couple of examples based on my reputation history for March, 30 (that's yesterday, yeah).

  1. Let's visit my reputation tab, select the "time" mode and check March, 30. Here's what you will see:

    Image showing correct reputation details in the "Time" view

    There're 5 upvotes and 1 downvote for the post about topbar.

  2. Now let's assume that the last time you have visited the tab, it was March 30, 20:00 UTC on the clock. You can click this link, since I know how to use a time machine and hence it's repro'able.

    Image showing ghost (non-existent) votes in the "Time" view; for example, the image shows 70 rep instead of 40 for the post about topbar on 31st March

    Oh wow, how cool is that? So how many upvotes have I got in total?

Conclusion: if there're some reputation changes that you haven't seen yet, the time tab shows them wrong. I prefer using the time tab sometimes, since it highlights the unseen rep changes with yellow which allows you to check how many votes ago I checked it.

  • 1
    Nothing new here, has been for ages like this. There must be a dupe somewhere out there.
    – Luuklag
    Apr 1 at 4:48
  • @Luuklag It seems all the reports about this gets closed as duplicates of this question. Here's one that got the status-norepro tag, but with the detailed information in this answer I hope that we'll see the status-reproduced tag on it.
    – Ted Lyngmo
    May 4 at 19:10
  • @ted meme: possible duplicate of nicael’s report. Cultural height: right in the duplicate banner
    – nicael
    May 4 at 20:07
  • @Ted there's no such tag. If the developer can reproduce, they can add status-planned if they actually plan to fix it soon, status-deferred if fix isn't on the near future timeline, but isn't rejected right away. status-declined if they deem the bug unworthy to fix, or status-review if they want to keep the bug in the waiting list and re-think the next step at some later point in the future. May 4 at 20:15
  • @nicael I'm sorry, but I don't understand what any of that means (English is not my first language).
    – Ted Lyngmo
    May 4 at 20:38
  • @ShadowWizardSaysNoMoreWar "there's no such tag" - Do you mean status-reproduced with the description "Indicates that the site developers were able to replicate the behavior reported, but cannot address its cause at this time"?
    – Ted Lyngmo
    May 4 at 20:38
  • @TedLyngmo yes. May 5 at 8:22
  • @ShadowWizardSaysNoMoreWar I don't understand what "there's no such tag" means when referring to a tag that exists.
    – Ted Lyngmo
    May 5 at 10:46
  • 1
    @Ted LOL, my bad this time. I honestly forgot this tag exists, because it's simply never used. I wanted to ask to burninate it long ago and forgot. Thanks for reminding me, this time I might actually post such request. Sorry for the confusion! :) May 5 at 13:10


You must log in to answer this question.

Browse other questions tagged .