7
$\begingroup$

A somewhat common pattern on this site seems to be that a new user will post a poor question, receive a bunch of downvotes and have their question closed. If we're lucky, they'll (or someone) improve their question and it will be reopened. However, the initial downvotes will remain, many (if not most) of which may have been regarding presentation or context issues that were corrected in the edit, rather than the intrinsic value of the question. It is, unsurprisingly, also not too uncommon to see new users encountering this situation complain in the comments about how many downvotes their getting before they have a chance to improve their question - and, unfortunately, the best counsel to offer such users is to improve it anyways and hope that other people will upvote it afterwards.

To address this issue, I suggest the following:

If a question is closed, edited, then reopened, anyone who cast a downvote on it should be pinged to look at the question again.

This feature would help to ensure that downvotes remain justified, even after the content to which they apply changes. However, given that it would only be triggered after an edit and 5 reopen votes cast by 3k+ users (presumably an edit which causes reopening), there would already be considerable evidence that the community has changed its opinion on the question before this feature would be activated. I doubt that this would become an annoyance, even to prolific downvoters, since reopening is not too common, and if such pings became excessive, one could constrain it to only apply to new questions or new users or significant edits. For new users, this feature could provide a "second chance", a greater incentive to edit their questions, and less frustration with quick downvotes. In short, it would be a relatively simple way to improve the experience of new users, without burdening much the rest of the community.

$\endgroup$
  • 6
    $\begingroup$ Request for someone skilled with Data.SE: Create a query that would show how often this would ping. (i.e. In the past week, how many questions were edited and reopened?) If I got ~10 pings a day by this script, I'd probably be annoyed. $\endgroup$ – apnorton Jan 22 '15 at 23:57
  • 2
    $\begingroup$ "(...) and if such pings became excessive, one could constrain it to only apply to new questions or new users or significant edits. " I think this is unnecessary, the question has been reopened, that should be a good enough filter. $\endgroup$ – Git Gud Jan 22 '15 at 23:59
  • 3
    $\begingroup$ For people who want to watch out for reopened questions: the dropdown in the lower right of 10k Moderator Tools for closevotes can be used to find these. $\endgroup$ – apnorton Jan 23 '15 at 0:06
  • 4
    $\begingroup$ You are in good company: a similar request was made 5 years ago by Jon Skeet, and was declined: Allow an edit to notify downvoters: “I think I've fixed the issue now - please check”. However, yours is more specific in that it's about reopened questions only. $\endgroup$ – user147263 Jan 23 '15 at 0:41
  • 4
    $\begingroup$ @anorton I wrote a query here which should list all pings that'd occur last two weeks. It lists 204 pings (and should be an overestimate; voting times are rounded, but even just counting "downvotes on edited and reopened posts" is 215). In any case, that says 15 pings (sitewide) per day, which is not much at all. (It seems too low though - maybe my SQL's bad). Also, recall that, out of 40 votes/day, not very many will be downvotes on questions that will be editted and reopenned. $\endgroup$ – Milo Brandt Jan 23 '15 at 0:43
  • 1
    $\begingroup$ In some cases such pinging would speed up reclosure. $\endgroup$ – Jonas Meyer Jan 26 '15 at 0:58

You must log in to answer this question.

Browse other questions tagged .