Xref: utzoo news.groups:16092 rec.music.misc:38730 alt.flame:13689 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!bu.edu!bu-cs!buengc!bph From: bph@buengc.BU.EDU (Blair P. Houghton) Newsgroups: news.groups,rec.music.misc,alt.flame Subject: Re: Bill Vajk memorial ``DOESN'T GET THE JOKE'' award of 1990 goes to: Thom (What does ^Z do?) Rounds! Message-ID: <5184@buengc.BU.EDU> Date: 3 Jan 90 19:52:37 GMT References: <1990Jan1.194234.1679@lth.se> <24104@gryphon.COM> Reply-To: bph@buengc.bu.edu (Blair P. Houghton) Followup-To: news.groups Organization: Boston Univ. Col. of Eng. Lines: 32 In article TAR@MAINE.BITNET (Thom Rounds) writes: >NOBODY saw the call fo Votes, and only a few people saw the >call for Discussion. Now, take those facts and all the things you've said and >done in the past, and what do you get? A pretty piss-poor job of trying to blame Dickie for your screwup. Thom, a cancel message, especially one from a distant node, takes time to propagate itself and to do its work. Further, it leaves a trail of its own. Therefore: a. Some number of people would see your article before it was cancelled; and, b. There would be a record of the cancellation. So. There may yet be nodes where they article still exists, no matter whether it was cancelled or not, and there should be nodes with big disks where the cancel request exists unexpired. You can go whining to news.admin for some kind soul to help you track down the evidence. Besides, I don't think Dickie could do such a thing this cleanly. I'd look for a trail of aged water, killifish fry, and wristwatch parts leading halfway down the hall if I suspected him of sabotaging something of mine. --Blair "Have your lawyer call my lawyer and we'll do discovery."