Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site sdcsvax.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!tektronix!hplabs!sdcrdcf!sdcsvax!jww From: jww@sdcsvax.UUCP (Joel West) Newsgroups: net.news,net.news.group Subject: Re: Removing net.flame Message-ID: <977@sdcsvax.UUCP> Date: Thu, 11-Jul-85 12:45:00 EDT Article-I.D.: sdcsvax.977 Posted: Thu Jul 11 12:45:00 1985 Date-Received: Wed, 17-Jul-85 05:30:01 EDT References: <3892@alice.UUCP> <484@oliveb.UUCP> <268@luke.UUCP> <1304@cbosgd.UUCP> Organization: CACI, Inc - Federal, La Jolla Lines: 36 Xref: watmath net.news:3633 net.news.group:3262 > net.flame was created to give the flamers a place to post so they > would keep their flames off the other newsgroups. For the most > part, this has worked well. If we remove net.flame, the flames > will just start to appear in other groups. > > One thing we could do is forbid (in software) cross posting to > net.flame and anything else. We could refuse to accept or forward > such postings, just like moderated groups. This would help keep > flames from spilling out into other groups. > > Mark Horton This is the best solution I've seen. This should probably be configurable through a system administrator-controlled file, so that the net can clamp down on other cross-postings without requiring a new version of netnews. After all, it's already being done in some cases with net.general. I also agree with the previous remarks that suggest forcing followups to multiple news groups to be verfied, as in the mock dialog: The following newsgroups are given; please choose only those necessary: net.news[n]? net.news.group[n]? net.women[n]? net.religion[n]? Of course, the default action of many carriage returns would specify NO newsgroups, which could be the same as "cancelled". Joel West CACI, Inc. - Federal (c/o UC San Diego) {ucbvax,decvax,ihnp4}!sdcsvax!jww jww@SDCSVAX.ARPA