Gnus development mailing list
 help / color / mirror / Atom feed
From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: yEnc support in Gnus?
Date: Wed, 03 Jul 2002 20:44:18 -0400	[thread overview]
Message-ID: <m3hejgjp99.fsf@peorth.gweep.net> (raw)
In-Reply-To: <m3pty4l7zh.fsf@merlin.emma.line.org> (Matthias Andree's message of "Thu, 04 Jul 2002 01:14:26 +0200")

* Matthias Andree <ma@dt.e-technik.uni-dortmund.de>  on Wed, 03 Jul 2002
| "Broadcast" is not to be seen in the strict and network-layer oriented
| sense. NNTP is being (ab)used for binary distribution, it carries data
| regardless of whether this data has been requested or not.

Not true.  Every news server requests the contents of a list of newsgroups
from its upstream server(s).  For example, back when I was a news admin, my
site wanted all binaries groups except the pictures groups.  We wanted to
avoid possible copyright problems with the picture groups.  My newsfeeds
file had "alt.*" and "!alt.binaries.pictures.*", requests to the upstream
servers to send us everything in alt, including the binaries groups, but
excluding the pictures groups.

By default, a feed in a newsfeeds file requests no news at all.  The news
server admin must fill in a list of groups that his server will carry, even
if that list is simply "*".  Additionally, the news server admin must
manually perform newgroup commands, or configure his server to automaticaly
perform them or ignore them entirely.

You may want to argue implicit vs. explicit, but there is no such thing as
unrequested news.

-- 
Rat <ratinox@peorth.gweep.net>    \ If Happy Fun Ball begins to smoke, get
Minion of Nathan - Nathan says Hi! \ away immediately. Seek shelter and cover
PGP Key: at a key server near you!  \ head.
       That and five bucks will get you a small coffee at Starbucks.



  reply	other threads:[~2002-07-04  0:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-27 16:35 Ted Zlatanov
2002-06-27 16:48 ` Matthias Andree
2002-06-28  8:58   ` Per Abrahamsen
2002-06-30 10:16     ` Matthias Andree
2002-06-30 17:49       ` Per Abrahamsen
2002-07-01 16:11         ` Ted Zlatanov
2002-07-01 21:08           ` Florian Weimer
2002-07-01 19:34         ` Simon Josefsson
2002-07-02  1:47           ` Russ Allbery
2002-07-02 10:51             ` Steinar Bang
2002-07-03  1:25               ` Russ Allbery
2002-07-02 11:47         ` Matthias Andree
2002-07-02 12:52           ` Kai Großjohann
2002-07-02 15:37           ` Stainless Steel Rat
2002-07-03 23:14             ` Matthias Andree
2002-07-04  0:44               ` Stainless Steel Rat [this message]
2002-07-04  7:49                 ` Steinar Bang
2002-07-05 13:53                   ` Stainless Steel Rat
2002-07-04 14:14                 ` Matthias Andree
2002-07-04 15:50                   ` Per Abrahamsen
2002-07-05 14:03                   ` Stainless Steel Rat
2002-07-11  8:56             ` Gerd Flaig
2002-07-01 21:07       ` Florian Weimer
2002-06-27 18:02 ` Simon Josefsson
2002-06-27 18:24   ` Stainless Steel Rat
2002-06-27 18:37     ` Ted Zlatanov
2002-06-30 10:19       ` Matthias Andree
2002-08-07  2:03   ` Jesper Harder
2002-08-07  8:22     ` Per Abrahamsen
2002-08-07 10:14     ` Simon Josefsson
2002-08-08  3:02       ` Jesper Harder
2002-08-15 10:18       ` Matthias Andree

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3hejgjp99.fsf@peorth.gweep.net \
    --to=ratinox@peorth.gweep.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).