Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!husc6!uwvax!oddjob!gargoyle!ihnp4!cbosgd!cwruecmp!hal!ncoast!allbery From: allbery@ncoast.UUCP (Brandon Allbery) Newsgroups: news.admin Subject: Re: Expiration dates on OtherRealms Message-ID: <3724@ncoast.UUCP> Date: Sat, 1-Aug-87 18:52:14 EDT Article-I.D.: ncoast.3724 Posted: Sat Aug 1 18:52:14 1987 Date-Received: Sun, 2-Aug-87 20:27:52 EDT References: <2525@hoptoad.uucp> <21616@lll-tis.arpa> Reply-To: allbery@ncoast.UUCP (Brandon Allbery) Followup-To: news.admin Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 19 As quoted from <21616@lll-tis.arpa> by mcb@lll-tis.arpa (Michael C. Berch): +--------------- | I tend to agree with Chuq on this. He is using the "Expires:" field | for exactly the purpose for which it was intended: when the | author/poster of an article believes that it is of some more lasting | use or value as opposed to the normal flood of Usenet articles. +--------------- I second this, especially since I'm doing the same thing in comp.binaries.- ibm.pc now. Specifically: the constant requests for PKXARC and UUDECODE, which eat up a LOT of net bandwidth in both news and mail, plus the responses to them which eat up even more of both. So I post once a month (for the benefit of new sites) and the stuff I post has an expire date 5 weeks in the future. Once a month is better than 3 times a day by any scale of measurement. -- Brandon S. Allbery, moderator of comp.sources.misc and comp.binaries.ibm.pc {{harvard,mit-eddie}!necntc,well!hoptoad,sun!cwruecmp!hal}!ncoast!allbery ARPA: necntc!ncoast!allbery@harvard.harvard.edu Fido: 157/502 MCI: BALLBERY <>