Correcting users

[Patton Echols]

On 01/31/2010 10:39 AM, Amedee Van Gasse wrote:
> On 31-01-10 18:18, Gilles Gravier wrote:
>   
>> Hi!
>>
>> On 31/01/2010 17:27, Johnneylee Rollins wrote:
>>     
>>> What's our policy on correcting bad advice or even, God forbid,
>>> dangerous commands?
>>> I'd like to know, and I'd like Karl to know this as well. He can't
>>> seem to read and comprehend the CoC
>>>
>>>
>>>       
>> Use common sense. If somebody posts bad advice, just post a reply to it
>> and explain why it is bad, what are the risks, etc...
>>     
>
> I would like to add that you don't have to correct somebody when 
> somebody else has already corrected the first person. Except of course 
> when the correction is also incorrect or incomplete.
>
> In other words: first read the entire thread before you write an answer.
>
> My €.02 :)
>
>   
Also, without ad hominem attacks.  There is a huge difference between 
"That is wrong because $a, $b, $c . . ."  and "Any idiot would know that 
$a, $b, $c, so you clearly are not as smart as an idiot . . ."  The 
former is helpful to future readers, the latter will be seen as  "orange 
noise."  (White noise with flames!)