1994-05-12 - Re: low-quality posts

Header Data

From: Cyber City <cyber1@io.org>
To: cypherpunks@toad.com
Message Hash: 0a0a43aa2cdc2eefc6544b4de0927dc994b64753e98c1e4c881837f50176f41e
Message ID: <Pine.3.89.9405121659.A20845-0100000@io.org>
Reply To: N/A
UTC Datetime: 1994-05-12 20:19:04 UTC
Raw Date: Thu, 12 May 94 13:19:04 PDT

Raw message

From: Cyber City <cyber1@io.org>
Date: Thu, 12 May 94 13:19:04 PDT
To: cypherpunks@toad.com
Subject: Re: low-quality posts
Message-ID: <Pine.3.89.9405121659.A20845-0100000@io.org>
MIME-Version: 1.0
Content-Type: text/plain


Derek Upham <upham@cs.ubc.ca> wrote:

> There are two ways to filter for content: filter at the newsgroup
> source via moderators, or filter at the newsgroup destinations via
> killfiles.  Moderating does seem to get rid of most of the cruft, but
> the moderators are required to read every post that comes through,
> and, worse, make judgements with some degree of impartiality (which is
> not always possible).

There's a simpler solution.  Using the majordomo hack I posted earlier,
mail from known abusers would be bounced to the moderator for his
approval or rejection.  This would be a small volume, which should
be within the capabilities of one moderator.

It's important to note that even abusive posters have their moments
of lucidity.  For example, one or two of Detwelier's posts were
actually worth reading.  So a wholesale and automatic filtering
would be wrong.

As for the marginal stuff, it should be passed for redistribution,
and the end-users should be educated on means to do their own
filtering.  For example, here's a simple scheme to employ the
filter distributed with ELM:

.forward file: "|/path/to/filter -vo $HOME/.elm/filter-errors"

.elm/filter-rules file:

if (from = "lassie") then save "~/mail/nal"
if (to contains "cypherpunks") then save "~/mail/Cypher"

--
Alex Brock






Thread