I tend to agree with this - it looks bad, provides no real advantage to anyone other than a moderator investigating the root cause of the problem, and actually offers a reverse-engineering tool to folks intentionally looking to game the system.
Hiding it by default, visible only to moderators and profile owners via the "show deleted posts" checkbox, makes ...
This happens when a post that gave you sufficient rep to give a bounty was subsequently removed.
After a rep-recalc, the system finds that you no longer had enough rep to "have given" the bounty. But of course it can't turn back time and change the past. Instead, it gives you that rep for free.
So a sequence of events such as this: (the exact numbers will ...
What are all the event types and what do they mean?
upvote / downvote - Your post was upvoted or downvoted.
unupvote / undownvote - An upvote or downvote previously cast on the post was retracted.
downvoted - Note the extra "d" at the end; you cast a downvote on an answer. Downvotes you cast on questions are not shown in your reputation history and do not ...
Today I discovered by accident that this information is (sometimes) visible in your personal timeline/feed in the Stack Exchange app:
These two -10s corresponds to this -20 "user was removed" entry in my profile:
That means it's available via the Stack Exchange API, using the Reputation History call:
Go to this page
Change the site with the  link (...
Unexplained changes in reputation are often reported when deletion is involved. Such changes are hidden by default, but it is possible to see them by enabling the "show removed posts" option on the bottom of your profile's reputation tab.
There are two main types of deletion for the purpose of this post:
deleted posts When a post gets deleted, the votes ...
The blog post Reputation and Historical Archives describes displaying reputation lost from deleted questions as a privacy violation.
Second, we won’t display reputation lost to deleted questions on your
profile unless you explicitly ask for it, and won’t display it at all
to other people (apart from moderators). This was an egregious privacy
We can't easily hide these entirely; it would break the accounting for the reputation history in ways that would make it more difficult audit, which is sorta the whole point of having it public in the first place.
That said, we can make it less of a public wagged finger:
...which links to this page in the help center, which documents the various reasons ...
I've confirmed/reproduced the issue behind this. It is as I said. When you have new and old events on the same post in your history (only tested for the same day as well), both of them will expand to show the full list of all events for the post, rather than being limited to the new and old events as they're split up.
They must have made a change somewhere ...
There are 2 sides to this coin:
A real spammer whose account serves no purpose other than to spam the site. I fail to see the value of adding this info. The account would most likely get destroyed soon, so the info would only be available for a brief period of time.
A legit user who made an innocent mistake, or thought promoting his product on various ...
so if I check his reputation history, I must see a -1 on his reputation at the same time when I got downvote.
The Stack Exchange developers have been smart enough to acknowledge that easy way to see user's voting patterns, so downvotes mentioned on your profile are only visible to you, not to other users.
There are other ways though to try to find who ...
Looking at your per post reputation breakdown yesterday you received:
23 answer upvotes at +10 each.
2 answer downvotes at -2 each.
1 accept at +15.
At a guess, you downvoted other answers 3 times at -1 each.
2 of those upvotes didn't give you any reputation at all as they were cast after you hit the cap. 1 of those upvotes only gave you +7 points; we ...
No there is no option to hide negative reputation in our reputation history. Why do one need to hide it? If you have negative reputation, don't care of what people will think, just accept it and move on.
An often-forgotten effect of the "spam" and "rude or abusive" flags are that they impose a -100 penalty on the author of the post if they're actioned (that is to say, if enough spam/abuse flags result in the deletion of a post).
This means that if you post some reasonable questions or answers and then follow them up with, for example, an answer that's ...
In my duplicate question, I suggested we deal with this like this:
Apparently, users constantly accept, then unaccept, then accept answers — usually doing all three within seconds of each other. Similarly people upvote, then un-upvote, then re-upvote again, within seconds. See the image below.
As engineers, we know that the usual response to ...
We now rollup in a fairly simple way: if there are 2 of a reversible vote type, we hide that group if it's within the context of a day. We won't hide something accepted yesterday then unaccepted today for example.
If you accept/unaccept, that's hidden as there's no net-effect. Behind the scenes this is really one vote with a DeletionDate set...so we can ...
There were no net reputation changes on this day
There was a downvote that was then reversed, there was a change you may have momentarily noticed (why we show the message at all, it's also technically very hard to remove) but no net changes on that day.
I'm pretty sure this isn't a bug.
Other people can see the down-votes you've received on your profile. After all if they go to the post the can see the vote breakdown (assuming they have enough rep of course).
It's only the rep loss due to down-votes given that they can't see.
This is by design. A user can never go below 1 reputation, any downvotes when the user is at 1 are not generally not recorded if they are the only events in a day.
Take this user for example, or this one. All they received is downvotes, so nothing is recorded in the reputation history.
The user you found made one accept, then got downvoted again.
Hmm, I missed this request earlier - definitely could be better.
Starting with the next build the no-value row above will be removed (the (0) one will remain) and the tooltip will indicate it was your own answer.
In the case above there was a very old bug that allowed people to offer a bounty worth more than their current rep. To fix our mistake we have credited back any rep that would have pushed the running reputation below 1.
There were reputation changes that day, but the posts causing the changes have since been removed.
When viewing your own history, you can check the box "Show removed posts". However, that is not available when viewing other users' histories.
Edit: Additionally, since you can't see other users' votes, it's possible you're seeing this because the user's only ...
Votes and accepts that are undone within the same UTC day are coalesced and will not show up in the rep history.
When the new rep system was implemented, every single action was shown - including all the "bouncing" votes. So they were later all merged together.
The bug is different than described...the votes don't appear on any site until a recalc.
The vote recording code doesn't record a target for that vote (since reputation-wise, it doesn't matter). However, as part of many things that happens on a recalc, the owners get fixed up and then the rep history items get created.
Starting with the next build, we'll ...
Note that this feature-request is the opposite of this bug report, where some "-100"'s were accidentally shown to other users.
I happen to agree with Nick's view that;
... we are giving users the benefit of the doubt that they can be better here as we always do - we feel hiding it from the world (but still visible to the user and moderators) is the ...