Skip to main content
Commonmark migration
Source Link

I recently flagged an answer because I (erroneously, as it turned out) believed it to cause harm. The flag was declined on the ground that the purpose of a flag is not to judge technical content. Agreed. However, what if the advice really causes harm (say, it bricks a device)? What about malicious advice as in the following scenario:

Q: I am a newbie and I need help on xyz.

 

A: yada yada yada ... and rm -Rf / will do what you need.

I recently flagged an answer because I (erroneously, as it turned out) believed it to cause harm. The flag was declined on the ground that the purpose of a flag is not to judge technical content. Agreed. However, what if the advice really causes harm (say, it bricks a device)? What about malicious advice as in the following scenario:

Q: I am a newbie and I need help on xyz.

 

A: yada yada yada ... and rm -Rf / will do what you need.

I recently flagged an answer because I (erroneously, as it turned out) believed it to cause harm. The flag was declined on the ground that the purpose of a flag is not to judge technical content. Agreed. However, what if the advice really causes harm (say, it bricks a device)? What about malicious advice as in the following scenario:

Q: I am a newbie and I need help on xyz.

A: yada yada yada ... and rm -Rf / will do what you need.

Source Link
countermode
  • 7.7k
  • 10
  • 9

What to do about dangerous or malicious advice in an answer?

I recently flagged an answer because I (erroneously, as it turned out) believed it to cause harm. The flag was declined on the ground that the purpose of a flag is not to judge technical content. Agreed. However, what if the advice really causes harm (say, it bricks a device)? What about malicious advice as in the following scenario:

Q: I am a newbie and I need help on xyz.

A: yada yada yada ... and rm -Rf / will do what you need.