Skip to main content
34 events
when toggle format what by license comment
Jun 3, 2020 at 13:30 history edited CommunityBot
Commonmark migration
Oct 30, 2019 at 10:58 comment added user447378 The yellow mark on "rejected" and the green mark on "approved" - I think they are great - too bad they're gone :(
May 23, 2017 at 12:35 history edited CommunityBot
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Mar 20, 2017 at 10:30 history edited CommunityBot
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Mar 20, 2017 at 9:39 history edited CommunityBot
replaced http://meta.stackoverflow.com/ with https://meta.stackoverflow.com/
S Dec 17, 2014 at 20:35 history suggested CommunityBot CC BY-SA 3.0
Suggested edit outcomes are now shown in the activity list
Dec 17, 2014 at 19:33 review Suggested edits
S Dec 17, 2014 at 20:35
Aug 21, 2014 at 20:10 history edited Shog9 CC BY-SA 3.0
added 1328 characters in body
Apr 24, 2014 at 13:37 history edited CommunityBot
Migration of MSO links to MSE links
Apr 11, 2014 at 19:12 comment added mhlester @boltClock, nothing wrong with burning the candle at both ends though, right? Less crap gets robo-approved if there's less crap submitted
Apr 11, 2014 at 16:12 comment added BoltClock's a Unicorn Good thing robo-reviewers only approve stuff, not reject them... right?
Apr 11, 2014 at 15:53 history edited Shog9 CC BY-SA 3.0
better make this explicit, since there's a reasonable chance half of us have forgotten why it was implemented
Apr 11, 2014 at 15:51 comment added mhlester That's fantastic. I love it! Fingers crossed for an implementation. It really does seem like it could help a lot. Would have helped me in my infancy.
Apr 11, 2014 at 15:49 comment added Shog9 See edit, @mhlester. This is based on the flag warning thing, but with some variations due to the nature of the system.
Apr 11, 2014 at 15:47 comment added slhck I fully agree with this proposal. Just something needs to be done here, I don't have any strong preferences for the way it's done or the specific calculations.
Apr 11, 2014 at 15:32 history edited gnat CC BY-SA 3.0
quote background and tooltip for screen shots
Apr 11, 2014 at 15:19 history edited Shog9 CC BY-SA 3.0
Flesh this out a bit
Apr 10, 2014 at 16:22 comment added mhlester @Shog9, given the success of the somewhat related Allow recovery from flag hellban, I feel this should be revisited. Would it be a dupe to post something like your answer here as a new feature request? Or does a bounty on this question make sense, even though it's your answer I want to see implemented?
Nov 13, 2013 at 12:41 comment added razlebe @shog9 This still seems like a super relevant feature request - any update on whether this is planned?
Jul 21, 2013 at 12:28 history bounty ended Manishearth
May 1, 2013 at 19:43 comment added UpAndAdam BUT there is something you can do about it! examine your behavior and change it or revisit it before yuo are banned.. Also like @DanDascalescu idea.
Nov 5, 2012 at 0:00 comment added Dan Dascalescu Well, what if you COULD so something about your rejected edit?
Oct 16, 2012 at 20:35 comment added Servy What will "rejected" link to? Will it be easy to see what edits have been recently rejected, and what the reasons have been? Perhaps this warning should include the most common rejection reason for recent rejected edits, rather than just a paraphrase of the minor edit rejection reason.
Jun 23, 2012 at 13:50 comment added Tim Stone I agree with this, although to be fair, Jeff's response was when you'd get Ol' Orange Slidy for a notification...which was pretty significant harassment. I hardly notice Lil' Blue Circly to begin with, so the negative impact that comes with an in-your-face taunt is probably a little less. A context sensitive warning makes far more sense either way though, to the point where I'd also recommend it for the edge case where someone has a few recent edits rejected and then hits 2000 reputation, since they'd still potentially need to brush up on what makes a good edit.
Jun 23, 2012 at 3:03 comment added jmort253 I also like this solution better because the message is displayed on the site where the problem edit occurred. Why tell me my Project Management SE edits suck when I'm making SO edits for which I have a great track record. +1
Jun 22, 2012 at 22:43 history bounty ended Gilles 'SO- stop being evil'
Jun 22, 2012 at 22:43 comment added Gilles 'SO- stop being evil' I disagree that notifications are inappropriate, but as long as the information reaches the user (as opposed to being hidden deep inside their profile, undiscoverable and difficult to reach even if you know where to look), I'm happy. I would prefer to see “you had N edits rejected recently:”, followed a list of the edits that the user hadn't yet been notified about. (@Matt Not a percentage, that's useless. And each rejection must be shown, not just when there are very many of tehm, otherwise you stop improvement after users have gone beyond mediocre.)
Jun 22, 2012 at 21:08 comment added Matt @Shog9: I'd prefer to describe it as "the icing on the cake" ;).
Jun 22, 2012 at 21:01 comment added Shog9 @Matt / slhck - sure, that's a fine suggestion. But it is, as you say, somewhat orthogonal to this feature-request.
Jun 22, 2012 at 20:49 comment added slhck Agreed with @Matt — Shog9, the initial suggestion by the currently top voted answer (namely showing exactly which edits were accepted or rejected) is not orthogonal to your approach, but would be a useful addendum for those who actually check their profile.
Jun 22, 2012 at 20:43 comment added Matt +1 I like this. But they still have the problem of being routed to their suggested edit feed, and not been able to see, at a glance, which of their edits were approved/ rejected. (e.g.) Can this also considered as been shown when their rejection rate reaches X% ("WARNING: A large percentage of your reject edits have been rejected"), to catch the people who get a/r/a/r/a/r/a/r...
Jun 22, 2012 at 20:35 comment added Shog9 @slhck: yeah, that's where this occurred to me actually. Aside: tired of running into users who make dozens of bad edits / leave dozens of bad flags and only realize too late that they've done anything wrong; banning (and in particular hell-banning) is the wrong way to deal with users who honestly do want to learn.
Jun 22, 2012 at 20:31 comment added slhck Oh, see, I haven't been thinking about this at all. That makes a lot of sense when put into context! It would probably make sense to add a similar message to the flagging dialog if $number of flags have been declined.
Jun 22, 2012 at 20:29 history answered Shog9 CC BY-SA 3.0