Xref: utzoo alt.flame:33240 comp.sys.next:17545 comp.sys.amiga.advocacy:3003
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!rutgers!rochester!pt.cs.cmu.edu!zardoz.club.cc.cmu.edu!ddj
From: ddj@zardoz.club.cc.cmu.edu (Doug DeJulio)
Newsgroups: alt.flame,comp.sys.next,comp.sys.amiga.advocacy
Subject: Re: the recent glut of Amiga-related posts
Message-ID: <13020@pt.cs.cmu.edu>
Date: 13 May 91 13:51:27 GMT
References: <1991May8.063518.5934@cunixf.cc.columbia.edu> <1991May9.044759.27402@daffy.cs.wisc.edu> <1991May12.230031.15898@fwi.uva.nl>
Organization: Castle Anthrax, Pittsburgh
Lines: 20

In article <1991May12.230031.15898@fwi.uva.nl> groenewo@fwi.uva.nl (Ferry van het Groenewoud) writes:
> Probably the postings were intended to go to both csaa and csn.

I don't think so.  This sort of problem crops up occasionally.  Somone
posts something of genuine interest to both groups.  Then a novice
user wants to post to just one of the groups, and does it by selecting
the "followup" option on their news software.  They figure that if
they edit the subject line, it's the same as a fresh posting.  So,
something only intended for one group ends up going to all of them.

I think this is what happened.  The original crosspost was fine.
*Some* of the followups were fine.  But some of the followups had a
different topic, and had *absolutely* nothing to do with the NeXT.
For a couple of days nobody said anything, and the volume of the
crossposted stuff grew, and grew, and grew.  Some people got short
tempers from this and started flaming vigorously.
-- 
Doug DeJulio
dd26+@andrew.cmu.edu (AMS/ATK mail)
ddj@zardoz.club.cc.cmu.edu (NeXT mail)