Xref: utzoo news.software.b:8057 news.admin:14769 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!mp.cs.niu.edu!rickert From: rickert@mp.cs.niu.edu (Neil Rickert) Newsgroups: news.software.b,news.admin Subject: Re: Important TESTED patch for dxrn/mxrn Message-ID: <1991May30.182405.16917@mp.cs.niu.edu> Date: 30 May 91 18:24:05 GMT References: <1991May24.082757@mccall.com> <1991May30.120936.1009@mccall.com> Organization: Northern Illinois University Lines: 56 In article <1991May30.120936.1009@mccall.com> tp@mccall.com writes: >The routine you describe existed in the previous version of C news. It read >the Date: lines produced by dxrn just fine. BTW, dxrn isn't my software, At least get your facts straight. The previous versions of C news did not look at the date. The result was that at various times our disks filled up with news several months old. Because we complained enough the Henry and Geoff listened, and are now protecting us from these disasters. >I'm just a user. And I don't want it to fix all permutations of Date: line If you are just a user, then the important thing is to get your own Date line correct. If you are a sysadmin, just ensure that news generated on your system leaves with a correct date. Since the date should be machine generated that can't be difficult. You don't have to correct the dates generated by the rest of the world - that is their problem. >the old version just fine. I don't have a problem with switching to the >official standard, but it would've been nice to find out about it other >than by having my news articles dropped on the floor. Like maybe, before >the change was made, so I (or the author) could've fixed dxrn in advance. I believe that the intention to be strict was announced about 3 months before the changes were released. >(I don't buy the idea that nobody would have fixed the software if advance >warning were given, I know I would have fixed dxrn even if the author >didn't.) Then why didn't you? >Yep, pretty typical of the C news community. You don't give a damn what >problems you cause others, as long as your software works. Must be another The number of articles I am not seeing now is probably much less than the number dropped when disks here or on my feed filled up with stale news. >It'd sure be gratifying for someone to admit that this changeover was badly >handled. At least then we'd have some indication that a little more effort OK. I will admit it. It was handled very badly, especially by people like . >will be put forth next time to avoid such a mess. (I'm sure there will be a >next time, since it is C news' mission to save the world from >non-conformant software.) Actually I think C news is more interested in avoiding being the cause of the problems created by flooding the networks with stale news. -- =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= Neil W. Rickert, Computer Science Northern Illinois Univ. DeKalb, IL 60115 +1-815-753-6940