Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site psuvax.UUCP
Path: utzoo!linus!decvax!harpo!eagle!allegra!psuvax!jdi
From: jdi@psuvax.UUCP
Newsgroups: net.followup
Subject: Re: More boiling water
Message-ID: <222@psuvax.UUCP>
Date: Fri, 2-Sep-83 11:54:40 EDT
Article-I.D.: psuvax.222
Posted: Fri Sep  2 11:54:40 1983
Date-Received: Fri, 2-Sep-83 22:38:53 EDT
References: <680@druny.UUCP>
Organization: Penn. State Univ.
Lines: 49

First of all, let me say that I am an optimist.  Note that this makes a big
difference in this kind of argument, and I think the pessimistic side has
already been amply represented.  I think there are a few basic problems that
will face the netnews community in a few months/years.

1) Too much news.
	For me, this is already happening.  I still can't keep up with
	net.micro, or net.unix-wizards, although I would like to.  How-
	ever, I think a little history is important on this issue.  From
	what little netnews history I know, the whole system started some-
	where (duke?) and from there spread out to encompass its now 10000
	some readers.  Throughout this entire expansion, which is still
	going on, people have been saying 'Gee, what will we do when XXX
	articles start coming'.

	The answer is simple:  The system expands as the volume increases!

		#1:  We started with old, slow, netnewsA.  newsA might take
		     3 MINUTES of cpu time to process ONE article, and it
		     used huge amounts of disk, etc...

		#2:  Now, we have netnewsB.  It can process an article in
		     several cpu SECONDS, and in addition is easier on the
		     system as a whole.

		#3:  As I see it, the more important issue here is phone
		     costs and transmission times.  Well, we now have news
		     batching, a good scheme of which can reduce phone times
		     by 75%!  In addition, transmission times are getting
		     faster and faster, and Ethernet type links (50 Kbaud)
		     are becoming more popular.

2) Too much garbage.
	Well, assuming we have solved problem #1 (or at least matched growths)
	#2 becomes much easier.  What is needed in netnewsC (or whatever) is
	a "by newsgroup basis" expiration scheme.  Instead of all articles 
	expiring after oh, say 2 weeks, have net.jokes expire in a week, and
	net.sources expire in 3 months.  This way each site can decide for
	themselves how long to keep each newsgroup.

     In any case, netnews MUST NOT BECOME CAPITALIST.  The entire idea of
Usenet is that it is Free, and available to everyone who would like to use
it.  Putting in fines, costs, and taxes would destroy the system.


	Replies invited,

					John Irwin
					{allegra, burdvax}!psuvax!jdi