2

I was just wondering, what should one do with potentially dangerous answers? I mean I have read before on Meta that I should just flag them up, however when I did so for this one I just got this:

declined - flags should not be used to indicate technical inaccuracies, or an altogether wrong answer

So what is the correct course of action other than just downvoting (which is something I always do for these sorts of answers) the answer?

3

As a moderator I have to consider how this question and answer might be cited as an example in the future by other people ("You said this was okay!", "You said I shouldn't flag these!") and in order to do that properly, we need to be specific about the type of danger being offered up:

  • Maliciously dangerous posts (eg something that tries to obfuscate an rm -rf /) should be flagged as offensive if their intent is clearly to do harm.

  • Accidentally dangerous posts should be fixed. A lot of solutions could be dangerous or at least make things worse if they were incorrectly typed in. It's only likely that an error like that makes its way into an answer organically without intent.

  • Potentially dangerous posts are the most awkward ones to separate out. If the person throwing the answer into their terminal doesn't read around the answer or adapt it, they might be about to learn a hard lesson.

    A number of commands that are potentially ruinous have trigger guards. rename has a -n flag, and you can comment out the -exec or -delete arguments on a find example so that the user can confirm they're seeing the right files before batch operating on them.

So really past outright attacks, we're just about making posts as good as they can possibly be. A warning or a guard might be the ticket but they aren't requirements.


This is a significantly different topic to Help or advice on how to manage misleading/inappropriate answers to an asked question because that really deals with answers that are not answers. If you see something that is not an appropriate answer, flag away. If it's also dangerous, all the more reason to send it to oblivion.

2

If the answer answers the question it is a correct answer and should be upvoted and not downvoted nor flagged. You can always edit the answer and add in bold this command is dangerous. Or leave a comment stating it is dangerous. But a correct answer is a correct answer ;)

If it does not answer the question you downvote it, flag it and/pr leave a comment.

If it is wrong you edit it and make it correct, or flag it as NAA and/or downvote it.

  • 1
    If it is wrong but attempts to answer the question then you should downvote and comment, not flag. One of the default decline reasons for flags is (as stated in the question) "flags should not be used to indicate technical inaccuracies, or an altogether wrong answer". – Seth Nov 14 '15 at 22:56

You must log in to answer this question.