Xref: utzoo news.misc:5076 news.software.b:5276 Path: utzoo!utstat!news-server.csri.toronto.edu!cs.utexas.edu!uunet!snorkelwacker!ira.uka.de!smurf!urlichs From: urlichs@smurf.sub.org (Matthias Urlichs) Newsgroups: news.misc,news.software.b Subject: Cancel notifications (Re: How to reduce "noise" on the net?) Keywords: noise, news, cancel Message-ID: Date: 31 Jul 90 08:34:54 GMT References: <1990Jul27.201053.18550@cunixf.cc.columbia.edu> <1990Jul30.032519.28644@clmqt.marquette.Mi.US> Followup-To: news.software.b Organization: University of Karlsruhe, FRG Lines: 23 In news.misc, article <1990Jul30.032519.28644@clmqt.marquette.Mi.US>, scott@clmqt.marquette.Mi.US (Scott Reynolds) writes: < < >(4) Should the poster be notified when his/her article is cancelled? < < If this happens, the part of the net that gets news and mail by the same < links will have an even greater load. < Assuming that the Cancel eventually travels back to the sender's news machine, it would actually make sense for the originating machine to note the fact that it did in fact cancel that article, and to notify (a) the author and (b) the news administrator on that machine, as to who, what, where, when, and why. (And since the notification won't travel very far in this case, there's no question of consuming bandwidth.) This might also help when some net.idiot (or net.fascist) wantonly issues Cancel messages for other people's articles. The above might be a reasonable addition to news programs, which is why I have crossposted this article to news.software.b. -- Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(Voice)/621227(PEP)