Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!snorkelwacker!usc!cs.utexas.edu!rutgers!uwvax!daffy!cat9.cs.wisc.edu!schaut
From: schaut@cat9.cs.wisc.edu (Rick Schaut)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Withdrawal symptoms...
Summary: Keep it moderated...PLEASE!
Keywords: no moderator
Message-ID: <4267@daffy.cs.wisc.edu>
Date: 9 Feb 90 04:05:02 GMT
References: <22685@usc.edu> <1990Feb6.191414.13982@eng.umd.edu>
Sender: news@daffy.cs.wisc.edu
Organization: U of Wisconsin CS Dept
Lines: 18

In article <22685@usc.edu> kjh@pollux.usc.edu (Kenneth J. Hendrickson N8DGN) writes:
| May I suggest that we un-moderate c.b.i.p?  There is no reason that I
| can think of why this wouldn't work.  We can post instructions on how to
| post programs, including shell scripts even.  We can heckle people who
| carry on discussions there.  

The day c.b.i.p becomes un-moderated is the day I hit the "u" key.  It's
just too damn easy to hit the "F" key when somone has pissed you off.  Let
the flames stay in alt.flame where they belong, and keep the traffic in
c.b.i.p down.

It's also too easy for someone to post a binary that's untraceable.
Un-moderating c.b.i.p is an open invitation to a virus peddler.

--
Rick (schaut@garfield.cs.wisc.edu)

Peace and Prejudice Don't Mix! (unknown add copy)