Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site tilt.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!tilt!smw From: smw@tilt.UUCP (Stewart Wiener) Newsgroups: net.news.group Subject: Re: Yet Another Newsgroup Streamlining Message-ID: <14@tilt.UUCP> Date: Thu, 8-Mar-84 04:46:51 EST Article-I.D.: tilt.14 Posted: Thu Mar 8 04:46:51 1984 Date-Received: Thu, 8-Mar-84 19:43:50 EST References: <290@oliveb.UUCP> Organization: Princeton Univ. EECS Lines: 26 The concept of net.ent isn't well-thought out. One particular irksome detail: net.sf-lovers is NOT just about books, it includes sf movies and tv. It therefore should be (if we assume net.ent, which I don't like for another big reason that will be explained): net.ent.sf net.ent.sf.startrek <- was net.startrek net.ent.sf.drwho <- was net.tv.drwho net.ent.sf.sw <- was net.movies.sw The reason I don't like the concept of net.ent is that it becomes MUCH too easy for an unfriendly systems administrator to say: "This whole bundle of stuff is frivolous, and we don't need to receive it on our machine." Wham! boatloads of newsgroups zapped by a !net.ent in the sys file. I like tree-style organization, but by going too far in (a) segregating serious stuff from everything else, or (b) segregating unserious stuff from everything else, we're making netnews vulnerable to those who want ONLY the serious stuff. (And those sites won't GET the unserious stuff to pass along to the next node.) The effort put into the list is appreciated, though. If we have something to attack pieces of, at least we're working towards a solution... -- Stewart Wiener :-) "Read and weep as did Princeton Univ. EECS :-) Alexander when he beheld {allegra,ihnp4!mhuxi}!princeton!tilt!smw :-) the glories of Egypt."