Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: yEnc support in Gnus?
Date: Thu, 04 Jul 2002 17:50:29 +0200	[thread overview]
Message-ID: <rjit3v3322.fsf@zuse.dina.kvl.dk> (raw)
In-Reply-To: <m3wusb60mx.fsf@merlin.emma.line.org> (Matthias Andree's message of "Thu, 04 Jul 2002 16:14:30 +0200")

Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:

> You're missing the point. Of course, the whole bunch is solicited, but
> you don't get to choose individual articles or files (but you do with
> HTTP/FTP).

And this is significant because?

I believe it should be up to the server administrators to decide, for
whatever reasons they might have.

For example, using a client/server protocol like HTTP or FTP for very
popular files like pr0n and warez would be stupid from a technical
point of view, when a flooding protocol like Usenet is way more
efficient for that kind of stuff.  On the other hand, using Usenet for
technical discussions is hopelessly inefficient, the interest is low
enough that a peer to peer or client/server protocol in most cases
would be more efficient. 

Of course, mirrors and caching muddles this somewhat, as it makes HTTP
and FTP look more like a primitive flooding protocol.  And NNTP can
easily be used in a pure client/server setup, just avoid giving or
accepting feeds.

However, technical issues alone aren't (and shouldn't be) the deciding
factor.  Many ISP's feel that offering local access to textual
discussions on Usenet is a worthwhile added value.  And some don't
feel the same way about popular groups for binaries, even if it makes
more sense from a technical perspective.  Other factors such as user
expectations, available software, and habbits also play a role on what
parts of Usenet to offer.



  reply	other threads:[~2002-07-04 15:50 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
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 [this message]
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=rjit3v3322.fsf@zuse.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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).