chuqui@nsc.UUCP (Zonker T. Chuqui) (10/10/84)
While working in some of the news stuff, I came across a couple of messages
in my history file that should have been expired but weren't. Looking at
them, I found that both of them (591@houxe and 581@houxe) had 'Expires:'
lines in them for the end of October. So far, no problem. Unfortunately,
both were advertisements for a house for sale in New Jersey that should
have been in nj.wanted. One was in net.wanted, the other (identical house)
was in net.wanted and net.general.
This, for some odd reason, peeves me. The 'Expires:' stuff needs to be used
VERY carefully. When someone uses it on an article that causes me to store
something I never should have seen in the first place, I get a bit
irritated. Someone who knows enough to use 'Expires:' certainly should have
known enough to NOT post outside of their regional area on something like
that, and DEFINITELY not to net.general.
Is there something we can do about 'Expires:' besides ignoring them or
tracking them down manually? In these cases the articles were small and no
big deal (inappropriate or not) but it's possible for someone to send
something huge to net.sources with a long expiration date and get sites
that don't know the software that well in deep trouble. I'd rather come up
with something better than simply setting -I on my expire.
chuq
--
From the Department of Bistromatics: Chuq Von Rospach
{amd,decwrl,fortune,hplabs,ihnp4}!nsc!chuqui nsc!chuqui@decwrl.ARPA
How about 'reason for living?'