Path: utzoo!hoptoad!amdcad!decwrl!labrea!husc6!psuvax1!burdvax!bpa!sjuvax!cc743810 From: cc743810@sjuvax.UUCP (Chuck Conway) Newsgroups: alt.flame Subject: Re: Proposal for addition to new versions of the news software. Message-ID: <1083@sjuvax.UUCP> Date: 18 Dec 87 04:47:21 GMT References: <22198@ucbvax.BERKELEY.EDU> <670@brandx.rutgers.edu> Reply-To: cc743810@sjuvax.UUCP (Chuck Conway) Organization: Front Street Racing, Inc Lines: 45 In article <670@brandx.rutgers.edu> webber@brandx.rutgers.edu (Webber) writes: + In article <22198@ucbvax.BERKELEY.EDU>, bryce@hoser.berkeley.edu (Bryce Nesbitt) writes: + > ... + > Some initial barriers I suggest are: + > + > (alt.flame vs. -anything else-) + > (rec.audio vs. sci.electronics) + > (comp.sys.amiga vs. comp.sys.atari.st) + > (talk.* vs. -anything not in talk-) + + This is absolutely silly. Crossposting to alt.flame (and redirection + of followups to same) is the only decent way to handle the flammage that + ideas such as the above inevitably generate. + + ----- BOB (webber@athos.rutgers.edu ; rutgers!athos.rutgers.edu!webber) I don't see any problem with cross posting FROM -anygroup- TO alt.flame, but messages shouldn't be able to be cross posted FROM alt.flame to -anygroup-. This might call for a new header line structure like [...] Newsgroups: rec.autos Crossposting: alt.flame, rec.autos.d [...] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this should be allowed, but [...] Newsgroups: alt.flame Crossposting: rec.autos.d, sci.electronics, soc.singles [...] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this should NOT be allowed (Just a guy with another "bright" idea.....) Chuck -- Chuck Conway, Mopar Pilot ...!allegra\ cc743810@sjuvax.UUCP -or- ...!rutgers!cbmvax!bpa!sjuvax!cc743810 ...!princeton/ "If it won't do 150 mph, take it back." -Corvette Engineering Group