The reminder message can link to the MSE FAQ guide for moderating comments.

The reminder can be omitted for users who don't have the flag privilege. (Or, we could allow post authors to flag NLN on comments on their posts even without 15 rep)

Ideally, comments that are truly no longer needed would get removed as fast as possible. Benefits: Less clutter, less possible confusion to readers, etc.

There are plenty of other related feature requests I'd really like to see happen. The point of this proposal is to take what could be the simplest first step possible (implementation-wise).

Synergy with Another Feature Request

See this feature request that "Obsolete comment flags should notify the original commenter in advance of moderators".

These two feature requests would complement each other to tighten the feedback loop workflow without requiring the commentor to follow the post, or the editor thinking they should create reply-ping comments like "thanks I edited" (for example, see this SEDE query of SO, which has over 46K such comments within 100 characters each, and this SEDE query of MSO).

In the case of canned comments, I propose that this would instead notify the reviewer who gave that review, and potentially also those who upvoted the canned comment, since more NLN flags are needed in proportion to number of comment upvotes. (I am not sure if this is easily implementable.)

Topically Related Posts

  • The explanation of the suggested edits review queue on the meta FAQ, and the fuller guide on reviewing that queue.

    • I edited them to add reminders to flag NLN where appropriate, but the review queue UI doesn't link to those pages, so they aren't very visible unless you really go look for them (speaking from experience).
  • Others related to comment cleanup, but they did not focus on the edit feedback loop: 1, 2, this one has a lot of good discussion.

  • Ideally, we wouldn't have as much need for a feedback workflow and posters would get feedback while writing their post (see the "Ask Wizard" posts and other ones related to reducing manual-work of teaching new users).

  • This other feature request is basically (oversimplifying here) a request for a dedicated/glorified UI/UX to do this. Unlike that one, this is just asking for some "road signs", which I think is much easier to implement, and a good first step (20%-of-the-effort, 80%-of-the-results kind of thing).

  • If you're hungry for even more feature requests in a similar vein, here's the search query I used when doing my research: is:question [feature-request] [comments] [edits] -[status-completed].

  • Bonus fun: if this is implemented, it will help prevent candidates for r/nocontext such as this.
    – starball
    Nov 25 at 5:52


You must log in to answer this question.

Browse other questions tagged .