Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!samsung!think.com!yale!bunker!hcap!hnews!129!26!Jack.O'keeffe From: Jack.O'keeffe@f26.n129.z1.fidonet.org (Jack O'keeffe) Newsgroups: misc.handicap Subject: Re: Uploads Message-ID: <18862@bunker.isc-br.com> Date: 16 Apr 91 20:46:59 GMT Sender: wtm@bunker.isc-br.com Reply-To: Jack.O'keeffe@f26.n129.z1.fidonet.org Organization: FidoNet node 1:129/26 - SoundingBoard, Pittsburgh PA Lines: 49 Approved: wtm@bunker.hcap.fidonet.org Index Number: 15017 [This is from the Silent Talk Conference] JW> I wish to ask you and anyone else who cares to comment a question: James, I did see the one series of 13 that was received here. It was interesting, but I don't think this echo is the appropriate way to distribute such voluminous material. Transmission of this echo east to London, north to Canada, and west to Australia and Hong Kong costs some folks a heap of money. They might opt to drop SilentTalk rather than pay for gratuitous transmission of such lengthy text files. Is that what you want to happen? And BBSs do not have infinite disk space to store such articles. They will rapidly scroll into the bitbucket and be lost forever. Size limits were placed on messages for a good reason. Segmenting messages as you are doing is a way to "beat the system", but at least one BBS I'm aware of does not tolerate this and simply tosses such stuff directly in the bitbucket. Likewise, people who are reading on-line can become quite upset upon encountering lengthy files chopped up and posted in an echo. A suggestion. Why not upload your files to Emerald Isle in an archive format, then post a message here in SilentTalk giving the file name and a BRIEF description of the content? This way anyone who is interested can Freq them and you will not be creating problems for all others. Another suggestion. If Emerald Isle isn't able to give you all the storage needed, archive them on a disk and supply them to anyone interested who sends you a formatted disk and a self-addressed stamped mailer. JW> I have just learned is that long uploaded messages requiring JW> sequential uploading can have the appearance of domninating JW> the echo. That's unintentional and I see the need to avoid JW> doing just that if it is indeed perceived that way. That's the way it is perceived, James. It appears that you are attempting to jam this echo. Especially since there are several more acceptable means of disseminating such information. ... Pax vobiscum. -- Uucp: ..!{decvax,oliveb}!bunker!hcap!hnews!129!26!Jack.O'keeffe Internet: Jack.O'keeffe@f26.n129.z1.fidonet.org