Edit - Meta Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Rev

2

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.
– slhck
Commented Jun 22, 2012 at 20:31
3

@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.
– Shog9
Commented Jun 22, 2012 at 20:35
5

+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...
– Matt
Commented Jun 22, 2012 at 20:43
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.
– slhck
Commented Jun 22, 2012 at 20:49
1

@Matt / slhck - sure, that's a fine suggestion. But it is, as you say, somewhat orthogonal to this feature-request.
– Shog9
Commented Jun 22, 2012 at 21:01
@Shog9: I'd prefer to describe it as "the icing on the cake" ;).
– Matt
Commented Jun 22, 2012 at 21:08
3

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.)
– Gilles 'SO- stop being evil'
Commented Jun 22, 2012 at 22:43
1

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
– jmort253
Commented Jun 23, 2012 at 3:03
4

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.
– Tim Stone
Commented Jun 23, 2012 at 13:50
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.
– Servy
Commented Oct 16, 2012 at 20:35
Well, what if you COULD so something about your rejected edit?
– Dan Dascalescu
Commented Nov 5, 2012 at 0:00
1

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.
– UpAndAdam
Commented May 1, 2013 at 19:43
1

@shog9 This still seems like a super relevant feature request - any update on whether this is planned?
– razlebe
Commented Nov 13, 2013 at 12:41
2

See edit, @mhlester. This is based on the flag warning thing, but with some variations due to the nature of the system.
– Shog9
Commented Apr 11, 2014 at 15:49
1

@boltClock, nothing wrong with burning the candle at both ends though, right? Less crap gets robo-approved if there's less crap submitted
– mhlester
Commented Apr 11, 2014 at 19:12

| Show 5 more comments

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »