Xref: utzoo alt.sources.d:210 comp.sources.d:4272
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!uc!nic.MR.NET!hal!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery)
Newsgroups: alt.sources.d,comp.sources.d
Subject: Re: moderation of alt.sources vs. automated harangues
Message-ID: <1989Oct29.170145.9549@NCoast.ORG>
Date: 29 Oct 89 17:01:45 GMT
References: <2024@convex.UUCP> <1989Oct13.192835.1330@talos.uucp> <459@laas.laas.fr>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery)
Followup-To: alt.sources.d
Organization: North Coast Public Access UN*X, Cleveland, OH
Lines: 21

As quoted from <459@laas.laas.fr> by news@laas.laas.fr (USENET News System):
+---------------
| Well, why not have an automatic filter program as moderator.  It would
| check whether the posting has lines of the form #!/bin/[c]sh, 'cut
| here', etc., and would only post those that conform (genrated by your
| favorite `shar' program :-).  The others could either be automatically
+---------------

I could find a use for that [ ;-) ], but alt.sources?  Foo.  One of the
reasons for alt.sources is the fact that things sent to us moderator types
have to include shars, fancy auxiliary headers, etc.; if I have a small-but-
useful script I'd like to share with others (as with "bg"/"fg") I don't see
much point in adding baggage that doubles the size of it.  :-(

++Brandon
-- 
Brandon S. Allbery:  allbery@NCoast.ORG, BALLBERY (MCI Mail), ALLBERY (Delphi)
uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu bsa@telotech.uucp
*(comp.sources.misc mail to comp-sources-misc[-request]@backbone.site, please)*
*Third party vote-collection service: send mail to allbery@uunet.uu.net (ONLY)*
>>>	 Shall we try for comp.protocols.tcp-ip.eniac next, Richard?	    <<<