Possible Duplicate:
New reputation is too verbose: upvote/unupvote, upvote again

With the new reputation update on Stack Overflow, I noticed I suddenly had a +65 / -45. Apparently a user was indecisive or over-clicking the accept button. This is reasonable information, but these 6 events happened all in the same minute (maybe even the same 3 seconds).

I tested this out on some poor unsuspecting soul by spamming the accept button:

enter image description here

I bet it's going to catch him off guard to see a big red -255 (albeit, next to a green +255) that basically means nothing.

If nothing else, this is a cheap way to be disruptive and probably shouldn't be possible. It might be a good idea to have some interval between events, maybe even 5 or 10 seconds, during which accept/unaccept isn't logged. Perhaps even forcing 5 seconds between accept/unaccept actions themselves might be an idea (like comment edits).

marked as duplicate by Nick Craver Mar 9 '12 at 11:53

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • Since I'm sure we're going to see many questions like "Why did I have so much reputation from a single accept?!?" or something along those lines, I happily upvote your question. – Alenanno Mar 2 '12 at 10:47
  • It turns out my test ended up as 58 events, all within one minute. I bet you could really screw up the recipient's /reputation page by overflowing the numbers if you were really bored enough. Same thing applies to "downvote/undownvote" events I believe. – user159834 Mar 2 '12 at 10:49
  • Ahah that would be too cruel. :D – Alenanno Mar 2 '12 at 10:51
  • I'm actually now seeing a lot of very similar feature requests with varying reception. I'll just let this post linger I guess and we'll see how things evolve with the new rep calc/display. – user159834 Mar 2 '12 at 23:19
  • Oops, just dropped by to delete this and saw "status-completed", thanks. – user159834 Mar 18 '12 at 22:57

Instead of an interval, un* actions could just remove the original action from the log if it's been less than 5 seconds.

So you can still accept the wrong answer than quickly unaccept, and since you probably didn't mean to accept it at first (you're unaccepting that fast for any reason other than testing/boredome) you can fully undo. The other user won't ever know their answer was accepted and then unaccepted and wonder why.

  • That's what I think, they should just condense the events/rep-change down to what matters. i.e. 4 accepts and 3 unaccepts === 1 accept, 1 event, 15 rep. – user159834 Mar 2 '12 at 22:03