Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site ttrdc.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!mgnetp!ltuxa!ttrdc!levy From: levy@ttrdc.UUCP (Daniel R. Levy) Newsgroups: net.news Subject: Re: cleaning up the net -- software solutions proposed Message-ID: <272@ttrdc.UUCP> Date: Sat, 13-Jul-85 21:05:23 EDT Article-I.D.: ttrdc.272 Posted: Sat Jul 13 21:05:23 1985 Date-Received: Sun, 14-Jul-85 09:27:43 EDT References: <2961@nsc.UUCP> Distribution: net Organization: AT&T Teletype Corp., Skokie, IL Lines: 29 Keywords: cross-postings, etiquette, enforcement chuqui@nsc.UUCP (Chuq Von Rospach) <2961@nsc.UUCP>: > >2) Article length restrictions: > With the exception of specific groups (net.sources.all, perhaps > net.bugs.all and net.unix-wizards) all messages will be restricted at > the inews level to 100 lines. We've been trying to figure out how to > restrict over-long signatures, excessive inclusions in followups, and > otherwise overly verbose messages. By simply limiting the total size of > the message, people will have to be more careful about that stuff > (myself included). Articles brought in from off-site can be either ^^^^^^^^^^^^^^^^^^ > truncated silently or (preferred) rejected and returned to the sender > so that they can re-edit it to an appropriate size. > At last the pot calls himself black as well as the kettles! FYI, this article was 104 lines long at my site. Don't forget the length of .signature files! I would suggest that the news software give the miscreant user a second chance to abbreviate his/her article if it proves to be too long, rather than throw- ing it completely away (arrrgggh!). Something like "TOO LONG, n lines" and returning the user to $EDITOR with a file containing the too-long article. Trun- cation would only result in trash being posted, worse than useless. from the crossposting synapses of dan levy, hacker at&t data communications products (aka teletype corporation) skokie, ill ..!ihnp4!ttrdc!(ttbcad!)levy