Re: ietf-nntp Initial draft FINALLY available
Thomas 'Mike' Michlmayr <mike@cosy.sbg.ac.at> Wed, 02 October 1996 21:26 UTC
Received: from cnri by ietf.org id aa07738; 2 Oct 96 17:26 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa22191;
2 Oct 96 17:26 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id
QAA25833 for ietf-nntp-outgoing; Wed, 2 Oct 1996 16:16:25 -0500
X-Authentication-Warning: pheasant.ACADEM.COM: majordom set sender to
owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by
pheasant.ACADEM.COM (8.7.5/8.7.3) with ESMTP id QAA25829 for
<ietf-nntp@PHEASANT.ACADEM.COM>; Wed, 2 Oct 1996 16:16:23 -0500
Received: from loewe.cosy.sbg.ac.at (loewe.cosy.sbg.ac.at [141.201.2.12]) by
academ.com (8.7.6/8.7.1) with ESMTP id QAA02193 for <ietf-nntp@academ.com>;
Wed, 2 Oct 1996 16:16:15 -0500 (CDT)
Received: from grizzly.cosy.sbg.ac.at (grizzly [141.201.2.153]) by
loewe.cosy.sbg.ac.at (8.7.4/8.7.3) with ESMTP id XAA05380;
Wed, 2 Oct 1996 23:16:00 +0200 (MET DST)
Received: (from mike@localhost) by grizzly.cosy.sbg.ac.at (8.7.3/8.7.3) id
XAA01891; Wed, 2 Oct 1996 23:16:00 +0200 (MET DST)
Message-Id: <199610022116.XAA01891@grizzly.cosy.sbg.ac.at>
Date: Wed, 2 Oct 1996 23:15:59 +0200
From: Thomas 'Mike' Michlmayr <mike@cosy.sbg.ac.at>
To: "William H. Magill" <magill@isc.upenn.edu>
Cc: ietf-nntp@academ.com
Subject: Re: ietf-nntp Initial draft FINALLY available
In-Reply-To: <199610022006.QAA19979@staff.dccs.upenn.edu>;
from William H. Magill on Oct 2, 1996 16:06:15 -0400
References: <199610022006.QAA19979@staff.dccs.upenn.edu>
X-Mailer: Mutt 0.41
Mime-Version: 1.0
X-PGP-Key: finger -l mike@cosy.sbg.ac.at
Sender: owner-ietf-nntp@academ.com
Precedence: bulk
On Oct 2, magill@isc.upenn.edu (William H. Magill) wrote: > I believe that the general concensus of folks at the INN tutorial here at > LISA this week is that "sucking feeds" are a bad thing. while i'm not exactly thrilled by the current implementations of "sucking feeds" (the really suck ;-), i don't think that the idea is a bad thing. > For one thing, most "sucking feeds" are not legit feeds in the first place, > but rather people running readers, or pretending to be runing readers, > which are in fact servers. true. > Usually, at least in my experience, "sucking > feeds" are created by people who really have no idea what they are doing or > how to do things the "correct" way - ie by signing up to receive a feed. now, this might work in the US, but in europe the telephone-costs are too high for such things. many people use sucking feeds as a substitute for an offline reader, connecting once or twice a day and downloading the newsgroups they are interested in for later local reading. this is the only reasonable way beside UUCP (which most providers in .at don't offer) to get access to newsgroups (if you pay 4 US$/hour for a local phonecall, you think twice about connecting). now there might be other ways to do this (a feed which makes compressed batches that can be downloaded via ftp or something along that line), but most of these require the cooperation of the ISP (which refused to install UUCP before, so you're most likely out of luck). > The bigest reason that sucking feeds are a bad thing for servers is that it > prevents the server operator from utilizing the little bit of control > capabilities which exist in the feeding side of news. on the other hand, an admin does have some control capabilites over the reading side of news just as well. > People who are running sucking feeds tend to believe that they have a right > to news right now, even though their actions are in direct conflict with > the desires and demands of others. of course, but this is mostly a problem of educating users. > Until there are some major changes in the news database strcture, NEWNEWS > as an optional command is a tolerable evil, preferrably something which can > be commented out. agreed. perhaps discouraging NEWNEWS will teach the implementors of "sucking programs" a lesson to teach their programs to behave properly. -- Thomas 'Mike' Michlmayr can not assert the truth of all statements in this article and still be consistent. <mike@cosy.sbg.ac.at>
- ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- Re: ietf-nntp Initial draft FINALLY available Evan Champion
- Re: ietf-nntp Initial draft FINALLY available Chris Caputo
- Re: ietf-nntp Initial draft FINALLY available James Fidell
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Rich Salz
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Ramanan
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Rich Salz
- Re: ietf-nntp Initial draft FINALLY available Rich Salz
- Re: ietf-nntp Initial draft FINALLY available Nat Ballou
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Bob Sloane
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Thomas 'Mike' Michlmayr
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Bob Sloane
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available William H. Magill
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Evan Champion
- Re: ietf-nntp Initial draft FINALLY available USENET news manager
- Re: ietf-nntp Initial draft FINALLY available Evan Champion
- Re: ietf-nntp Initial draft FINALLY available chris (c.) lewis
- Re: ietf-nntp Initial draft FINALLY available William H. Magill
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- ietf-nntp XHDR versus XPAT USENET news manager