Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mcvax!botter!klipper!biep
From: biep@cs.vu.nl (J. A. "Biep" Durieux)
Newsgroups: news.admin
Subject: Re: A possible solution to the Expires: problem
Message-ID: <837@klipper.cs.vu.nl>
Date: Mon, 3-Aug-87 03:50:15 EDT
Article-I.D.: klipper.837
Posted: Mon Aug  3 03:50:15 1987
Date-Received: Tue, 4-Aug-87 01:48:45 EDT
References: <1026@moscom.UUCP>
Reply-To: biep@cs.vu.nl (J. A. "Biep" Durieux)
Organization: VU Informatica, Amsterdam
Lines: 29

In article <1026@moscom.UUCP> jgp@moscom.UUCP (Jim Prescott) writes:
"(...)
"How about a new header line of the form:
"	Supersedes: message_id [message_id ...]
"When an article comes in with a Supersedes line news posts it normally
"and then does a cancel on the message_ids indicated. (...)

"Some problems I can see with this are:
"	- It is more bookkeeping to track the old message_ids.
"	- It might lead to longer expiration times being used (...).
"Some benefits are:
"	- Savings of disk space (...).
"	- One of the groups this would help would be newusers (...).
"	- It becomes easier to make sure that even sites with flaky
"	newsfeeds always have a recent copy of your article."

Sounds good! One remark: only the poster of the original article should
be able to post a superseding one.

About the bookkeeping: rn should have an option (no DeLorean this time,
Larry :-)) to do this easily (like the cancel command now). It would be
nice to be able to supersede instead of just cancel an article one wrote
and one isn't really happy with, or an article one isn't sure about it
really went out. Perhaps the superseding article should be cross-posted
to control.
-- 
						Biep.  (biep@cs.vu.nl via mcvax)
	Some mazes (especially small ones) have no solutions.
							-- man 6 maze