Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site pegasus.UUCP
Path: utzoo!linus!decvax!microsoft!uw-beaver!cornell!vax135!ariel!houti!hogpc!pegasus!avi
From: avi@pegasus.UUCP
Newsgroups: net.news.configuration,net.flame,net.news.group
Subject: net.news.config!!!!!!
Message-ID: <557@pegasus.UUCP>
Date: Mon, 3-Oct-83 00:12:27 EDT
Article-I.D.: pegasus.557
Posted: Mon Oct  3 00:12:27 1983
Date-Received: Tue, 27-Sep-83 03:12:41 EDT
Organization: AT&T Information Systems, Lincroft NJ
Lines: 16

I keep seeing articles in the "junk" newsgroup because they are posted to
net.news.config -- even though the name has been officially lengthened now
that newsgroups names are only limited to 14 characters PER component. Are
people posting to the old name out of habit or because their machine has not
yet been upgraded to news version 2.10* ?

This problem is probably going to get worse. New newsgroup names can (and
should) be explicit enough to signify the general meaning of the newsgroup
(with the possible exception of groups like net.motss -- which should
probably deliberately retain an obscure name if it is created). As a matter
of fact, it would be nice if groups like net.dcom and net.std were expanded
to more useful names that would encourage more (proper) usage. Has anyone
considered allowing partial matching of newsgroup names?
-- 
-=> Avi E. Gross @ AT&T Information Systems Laboratories (201) 576-3063
    suggested paths:	[ihnp4, allegra, hogpc, ...]!pegasus!avi