40

There's been some consternation about the new flagging, but I wanted to focus on the syntax for a moment. I think the current shift doesn't really fix anything and it seems to fall into the same trap SO Triage does

[By] consensus here on Meta, it has been decided that "Requires Editing" actually should be applied only to posts that the community can edit into shape, not posts that require editing by the original author. Such posts, it is argued, should be marked instead as "Unsalvageable" since the community can do nothing on its own to salvage them.

I don't want to debate the policy or the interpretation. I want to draw attention to the fact that there is currently a massive disconnect between the official guidance in the UI and the policy as it is enforced by the moderation team.

I don't want to focus on just one reason, however. I think flagging in general suffers from a poorly worded set of options. I wanted to try and address this so I mocked up what I think it should look like

New flag window

Key changes

Red flags make deletion obvious

A common problem I run into flagging spam is that people don't always understand why we red flag. I had someone make this quote on Politics under a post that was spam

Mine was not a flag, but rather a vote to delete. Just being "nice"

A red flag is a vote to delete (not in the same way as a Trusted User, but the same net effect). I also slightly expanded the verbiage for spam to include promoting a website (a ton of spam is of the "visit my website" variety). I also expanded rude/abusive to include flagging unintelligible content (a reason few people know about).

Closed and Duplicate

Let's not mix terminology. The blue box says closed. The privilege says closed. "needs improvement" is highly confusing because it dumps you into the close dialogue box. Not every close reason is reopenable, either. Let's tell people we want it closed, and make it clear that closure is not necessarily a death sentence for a question or mean.

Mod flags

We need people to understand how and why you should use these flags. I've had several mods tell me that they prefer detailed mod flags when there's any question about a post.

NAA/LQP

NAA/LQP

This has been endlessly debated, but I think we can make some minor improvements. Most people do not know when to use Low Quality Post flags. Some verbiage cleanup would help and I try to denote that LQP flags are marked helpful if the post is edited (something that is not obvious)

  • I think the wording should be slightly altered (I don't like "deleted" - makes parsing the result of the flag harder) but otherwise solid suggestion. – VLAZ Apr 17 at 19:19
  • As a separate thing, I'd really like the duplicate to not say "closed as duplicate". Yes, you basically get the same thing - blue box, can't be answered, the whole thing. However, I have a dream that one day curators and question askers would be able to join hands as sisters brothers and both agree that a duplicate is not a bad thing. To do that, we really need duplicates to be marked as other than "closure" because, honestly they sort of aren't. I consider duplicate marking an answer. Being in the same category as "cannot be answered" and "should not be answered" is very odd. – VLAZ Apr 17 at 19:21
  • 3
    Oh man. I love this. Please implement ASAP! It needs to say "deleted", @VLAZ, because that's what the flags request. – Cody Gray Apr 17 at 20:13
  • @CodyGray I know that's what it requests, but I dislike the wording. When I pick the flag "deleted for spam" it sounds like I'm flagging it because it is deleted. Yes, it makes sense if you read the text before but then you have to go back and read it in order to make sense of the flag text. Simply making it "delete as spam" makes it immediately clear what the flag would lead to. – VLAZ Apr 17 at 20:16
  • @curiousdannii I upvoted your answer on the other question. I think that will suffice for now. Thanks for the mention. – Machavity Apr 18 at 14:40

You must log in to answer this question.

Browse other questions tagged .