Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site t4test.UUCP
Path: utzoo!watmath!clyde!cbosgd!ulysses!allegra!bellcore!decvax!decwrl!sun!qubix!t4test!chip
From: chip@t4test.UUCP
Newsgroups: net.news.group
Subject: Re: New newgroup suggestion--Re: Permanent Postings
Message-ID: <1280@t4test.UUCP>
Date: Tue, 25-Dec-84 17:03:01 EST
Article-I.D.: t4test.1280
Posted: Tue Dec 25 17:03:01 1984
Date-Received: Sat, 29-Dec-84 01:49:18 EST
References: <33@angband.UUCP> <729@watdcsu.UUCP>  <165@unc.UUCP>, <17976@lanl.ARPA> <3176@alice.UUCP> <6662@brl-tgr.ARPA>
Organization: Intel Peripheral Comp Mfg, Santa Clara
Lines: 25
Summary: problems with permanent articles

> From: wmartin@brl-tgr.ARPA (Will Martin )
> Date: 19 Dec 84 16:48:19 GMT
> 
> This request brings up a concept I have long felt is needed in many news
> groups -- permanent postings.

Our experience tells us it is a nice idea, but tough to implement.  Locally
we have two kinds of newsgroups:  one type (loc.all) is exipred regularly,
and another (info.all) is never expired.  The info newsgroups are moderated
locally and contain reference information and documentation.  However, this
presumes that the information does not require revision.  That assumption
is a good and reasonable one--for a few weeks :-)  Maintanance of such is
non-trivial.

Even though I see problems with administering a permanent-article system,
the hooks are already there.  Rather than creating magic article numbers
which aren't removed (as Will suggested), an absurdly long expiration time
creates the same effect.  After a few weeks all other articles will expire
normally, and the unexpired articles would be the first ones a new user would
see.

-- 

Chip Rosenthal, Intel/Santa Clara
{cbosgd,idi,intelca,icalqa,kremvax,qubix,ucscc} ! {t4test,t12tst} ! {chip,news}