This is a follow-up to Terminate the grace period when a post receives a flag.
Terminating the grace period for flags was status-declined because it would be confusing for users as flags do not have any visible mark. However, it was suggested in the answer that terminating because of voting would make more sense. This is a feature request to implement exactly that: Terminate the grace period when a post's score changes, or when it receives a vote.
The benefits of implementing this would be
- As mentioned in the earlier post, flags, especially serious "red" flags, would not be invalidated by the sneaky edit of the poster.
- Currently, to terminate the grace period, we have to comment. It's time-consuming, and for those of us that don't have a userscript installed to add from a set group of comments, it's too cumbersome that we either have to joke in the comments or abandon doing it altogether.
- The longstanding Can't change vote if the answer was edited too quickly would fix itself.
The only downside to this I can think of is the potential increase in the number of revisions for a post. But for me at least, if I see that I don't have to rush against a five-minute window to correct typos in my newly typed question, I would make my edit more substantial. This is also assuming that the post does receive a vote and the grace period is terminated, which is usually not the case.
When a question is voted on the first minute of it being posted, either it's terribad and will be deleted eventually, taking all the revisions with it, or is stellar and those are few anyway. In other words, its two extremes of the spectrum, not the normal questions.
Therefore, among the similar solutions to this, like terminating with flags, recording every revision anyway etc. this seems like the best solution.
How does it sound?
