Xref: utzoo news.software.b:7842 news.admin:14526 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!jarthur!ucivax!orion.oac.uci.edu!ucsd!celit!billd From: billd@fps.com (Bill Davidson) Newsgroups: news.software.b,news.admin Subject: Re: Really funny jokes being missed Message-ID: <17898@celit.fps.com> Date: 21 May 91 00:46:22 GMT References: <28357D59.17BB@tct.com> <1991May20.204313.25340@decuac.dec.com> Followup-To: news.software.b Organization: FPS Computing Inc., San Diego CA Lines: 27 In article <1991May20.204313.25340@decuac.dec.com> mjr@hussar.dco.dec.com (Marcus J. Ranum) writes: >I personally don't care if my server spends 5% more time a day processing >news, as long as I don't have to spend any more time dealing with it. Some of us do. Some of us are lucky to get a computer that can handle the load even under ideal software conditions. >If you force a human to be really careful about dates, or worse, to read the >reject logs or argue about software issues in news.software.b, you've >wasted more time - human time - the time that matters. Ah, but most USENET headers are not human generated, including "Date: ". The software generating the article in the first place should have done it right instead of wasting the CPU cycles of hundreds of thousands of machines around the world receiving USENET. For the human generated headers, the posting software should worry about problem and decide wether to drop or correct them. The transport software is the wrong place for it. If the posting software deals with it then it is dealt with once, rather than ? X 10^6. The system I run news on has to do a lot of other things besides news including a lot of interactive stuff. When news is hogging CPU cycles, guess what? The people doing interactive work have to wait longer for responses. There goes the human time. --Bill Davidson