Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!UCONNVM.BITNET!SEWALL From: SEWALL@UCONNVM.BITNET (Murph Sewall) Newsgroups: comp.sys.apple2 Subject: Re: a site to auto forward comp.binaries. shall we go for it Message-ID: <9007232054.AA11901@apple.com> Date: 23 Jul 90 20:44:51 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: School of Business - U. of Connecticut Lines: 35 On Mon, 23 Jul 90 15:32:29 EDT you said: >There is a site at psu that gateways many of the bitnet groups. It is >trivial to add a mailing list at that site to take all messages and >automatically post them to the group. This is much better than forcing >some poor bastard to post everything by hand. But if APPLE2-L is sending anything it receives to comp.sys.apple2 then how do you prevent looping? If it doesn't loop, it's a good idea. APPLE2-L is edited for a reason; perhaps Chris will send you a copy of everything sent to APPLE2-L that he DOESN'T post for a month and you'll see why (as any Marine Sargeant will tell you, no matter what you do 10% of the people won't get the word :-) >Using Apple2-L is a bad idea. USENET should not be the slave of those >sites unwilling to carry it. Better to configure the USENET software to >forward postings where necessary. Much cleaner and better philosopically. APPLE2-L is somewhat older (and more reliable) than comp.binaries.apple2. which isn't even carried by all UUCP sites much less most Internet and BITNET hosts (take a peek at the APPLE2-L subscriber list -- all the ProLines receive the files from APPLE2-L, for example). Also, when comp.binaries.apple2 ARCHIVES let us know ;-) There are quite a few folks that don't care to pay for program files they don't want so they don't subscribe to either list. From time to time they INDEX the archive and GET what they want (and ONLY what they want). If the choice comes down to one versus the other, knowledgable folks would probably prefer an archive site. comp.binaries.apple2 is an efficient means of distributing to UUCP sites, but it hasn't any particular advantage (and some disadvantages) distributing to Internet/BITNET hosts. /s Murph [Internet] or ...{psuvax1 or mcvax}!uconnvm.bitnet!sewall [UUCP] + Standard disclaimer applies ("The opinions expressed are my own" etc.)