49

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 ...


41

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 [edit] link (...


19

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 ...


14

This was literally a > that should have been a >= in a rollup algorithm somewhere. New code has been deployed and the 1,383 users this affects will be fixed over the next few minutes.


14

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 ...


13

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 ...


12

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.


12

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 ...


12

It does show the vote, it just doesn't record a reputation loss because at the time it was cast, their reputation was 1 and could not go any lower. Users receive a reputation recalculation shortly after their suspension which is what restores their reputation to its correct value. It also restores reputation loss for downvotes or any other inconsistencies ...


11

Almost always, this is a post you edited before you had 2K that was deleted. You got the +2 for the suggested edit and when the post was deleted, you lost that rep.


10

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.


10

You made a suggested edit to that post that was approved, awarding you 2 reputation. https://stackoverflow.com/review/suggested-edits/8139284 The post was deleted, therefore you lost 2 reputation.


9

I would love to see all events in the timeline when they initially occurred. Entries that are rescinded / invalidated later should be struck out: In addition there could be entries in current timeline for such reversal events - discolored if they concern previous days to indicate they are not affecting reputation "today". That would reflect what actually ...


9

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. When ...


8

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 ...


7

A single user did not give you 10 rep points on your question, there were 2 users who were deleted approximately about the same time that both had upvoted it. The "User was removed" is showing an aggregation of both users being deleted.


7

This happens when someone casts a spam/offensive flag on your post which ends up getting declined. The automatic downvote(s) against you by the Community user get invalidated immediately and your reputation corrected, but for some reason it doesn't remove the downvote event from your reputation history. The system corrects this on its own via a process that ...


7

Apparently my view there had somehow gotten set to "time" rather than the default of "post". I don't remember touching that (or even noticing it existed), and now that I've seen the "time" view I'm mystified by what signal it's meant to provide, but clicking on the "post" sort fixed my problem.


7

The giveaway here is the last entry shown in that rep history: "Serial upvoting reversed" (now appears as "voting corrected"). When extremely unusual voting patterns are detected between two users, all votes between them may be revoked - including the Accept votes. That doesn't alter the Accept status - the answer was still marked as ...


7

The system doesn't give you a way to figure out which posts lost votes. A sufficiently-curious person could use SEDE, which is updated only weekly, to try to figure it out, I suppose (assuming the votes weren't also recent). On the full site (which is what your screen shot appears to be from), you get one "user was removed" entry for each removed user. So ...


7

This happens any time you have a reputation reversal that affects the current day. For accounting purposes, the votes that were reversed still have to be calculated as gaining reputation, or the reversal makes no sense. This also plays oddly with the reputation cap, because your progress towards the cap is stored in a denormalized field on the User (it is ...


6

As I can see from the yellow highlight, it was showing you the changes you hadn't seen on the 'Reputation' tab yet. After you saw them, it rolled them into one.


6

+5 on Stack Overflow (under the Stack Overflow logo). +2 on UX (under the UX logo). Those are aggregates for the day, across all sites. Under those, highlighted the actual change you have been notified about. Which is the +2 for UX. I see no bug.


6

You want a graph, you get a graph. It's holiday season after all: As you noticed, vote timestamps are missing time information, and data may be (up to) 7 days old since SEDE is refreshed once a week on Sunday morning. Notice the use of parameters to reuse the query for multiple posts. Editing them repeatedly gets rather tedious :)


5

His total is being summarized by question. This appears in the list: +80 8 hours ago upvote java.util.Date class with different approach for same date gives different output His most recent vote was eight hours ago, which he didn't receive points for, but he received 80 points from it before he reached the Rep Cap. This happened with several ...


5

There is no bug here. The mobile and desktop views differ in how they display votes, that is all. On the desktop, new votes are shown as distinct from old posts, and votes in each category are grouped per post, per vote type (downvotes separate from upvotes separate from accepts, etc.). If you have not looked at your reputation tab in a while, new votes for ...


5

The API uses Paging to prevent that to much data needs to be sent. When you make a call to any of the API end-points you start at page 1. So for my reputation history the first call (for page 1, the default) is this: /2.2/users/578411/reputation-history?site=stackoverflow which returns this: { "items" : [{ "reputation_history_type" : "...


5

This is just a matter of both the unaccept and re-accept coming in at the exact same time and throwing the system off. A simple recalculation of your account fixed the issue.


5

There is a tool called Stack Exchange Data Explorer that allows users to perform queries on Stack Exchange's databases. Although it's not graphical, the raw data can be used to create a graph. For instance, to view the voting history of the first ever Meta Stack Exchange question go to https://data.stackexchange.com/meta.stackexchange/query/new and run the ...


Only top voted, non community-wiki answers of a minimum length are eligible