Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!ll-xn!cit-vax!ucla-cs!srt
From: srt@CS.UCLA.EDU
Newsgroups: news.groups,news.misc,news.stargate,news.sysadmin,news.admin
Subject: Re: the USENET problems
Message-ID: <7116@shemp.UCLA.EDU>
Date: Fri, 10-Jul-87 12:52:52 EDT
Article-I.D.: shemp.7116
Posted: Fri Jul 10 12:52:52 1987
Date-Received: Sun, 12-Jul-87 12:01:50 EDT
References: <266@brandx.rutgers.edu> <15982@gatech.gatech.edu>
Sender: root@CS.UCLA.EDU
Reply-To: srt@CS.UCLA.EDU (Matthew Merzbacher)
Organization: UCLA Computer Science Department
Lines: 19
Xref: mnetor news.groups:1217 news.misc:739 news.stargate:245 news.sysadmin:295 news.admin:674

There are different kinds of moderation needed.  One type is source group
moderation.  The moderator is primarily responsible for seeing that the
postings are actually source code and don't contain any obvious Trojan
Horses.  A second type of moderation is used in opinion groups, where
moderation is used to winnow out uninformed opinions and repetitive comments.

I've suggested before that the first type of moderation can be handled by
forcing posting to source groups through a local (i.e., site) moderator,
normally the new administrator.  This is an additional burden on the
news admin, but since most sites rarely post more than one piece of source
a month, it would hardly be overwhelming.

This is even implemented quite easily; you change the moderator's address
to be the address of the local moderator.
 
    Scott R. Turner
    UCLA Computer Science     "I don't need your plastic hassles."
    Domain: srt@ucla.cs.edu
    UUCP:  ...!{cepu,ihnp4,trwspp,ucbvax}!ucla-cs!srt