SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : How to best deal with KOOKS at this web site

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: fut_trade who wrote (164)4/11/1997 9:39:00 PM
From: Iceberg   of 1894
 
>My personal feeling is that he should have been ignored.

>I am very interested in your opinion.

Peter,

This is my personal opinion:

The protocol for a type II post is not to ignore it, as you suggested.


What we do know is that skang posted a type II message (an earlier message than the one you referenced). Type II posts require a measured response as we've discussed on this thread. Such a response seems to be in progress as we speak.

I wouldn't assume that because someone says they got fired that they actually got fired. It could be a lie. It could be the truth. It could be something inbetween. The fact is, we simply don't know that skang was fired, and if he was fired, we don't know if it had anything at all to do with his SI posts.

This gets back to why we respond to a type II poster as we do.

Asking for, and receiving, data and referenceable material is much more convincing, plausible and less inflammatory than are nonreferenceable posts lacking verifiable data...such as a post simply saying one has been fired.

Again, this is just my opinion after a quick review of the series of posts you referenced. My opinion isn't intended to be directed at anyone personally.

If you have a differing opinion, please feel free to discuss it here. We're trying to develop response protocols to problem posts, and this is an interesting case in point.

Thanks.

Ice



Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext