Xref: utzoo news.software.b:7964 news.admin:14662 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!news.cs.indiana.edu!att!linac!mp.cs.niu.edu!rickert From: rickert@mp.cs.niu.edu (Neil Rickert) Newsgroups: news.software.b,news.admin Subject: Re: Really funny jokes being missed Message-ID: <1991May26.164321.19550@mp.cs.niu.edu> Date: 26 May 91 16:43:21 GMT Article-I.D.: mp.1991May26.164321.19550 References: <1991May26.082113@mccall.com> Organization: Northern Illinois University Lines: 27 In article <1991May26.082113@mccall.com> tp@mccall.com (Terry Poot) writes: >the RFC's before doing so. Are all your users required to read RFC822 and >RFC1036 before using news? Mine aren't, and I don't think they should be. I don't think users should be required to read RFC1036 either. But I do think news software developers should, and should make sure that articles entered into the news system with their software are compliant. >Given the wide range of date formats that B news handles, did you honestly >believe that there is no news software that generates any of them but the >one in RFC822? You are missing the point. There is a wide range of date formats that C news handles too. And when an article is submitted in one of these formats it is reformatted into an RFC compliant form. It just so happens that the design of B-news is such that this reformatting occurs at every B-news site, not just on article submission. If somebody produces software which incorrectly assumes that it can put out bad dates and rely on other software somewhere else to fix it, you should not blame C-news for the predictable result. -- =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= Neil W. Rickert, Computer Science Northern Illinois Univ. DeKalb, IL 60115 +1-815-753-6940