Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site mit-eddie.UUCP Path: utzoo!linus!vaxine!wjh12!genrad!mit-eddie!rh From: rh@mit-eddie.UUCP (Randy Haskins) Newsgroups: net.legal,net.micro Subject: Re: Computer Bulletin Boards Must Be Confiscated! Message-ID: <2028@mit-eddie.UUCP> Date: Mon, 4-Jun-84 17:21:48 EDT Article-I.D.: mit-eddi.2028 Posted: Mon Jun 4 17:21:48 1984 Date-Received: Wed, 6-Jun-84 02:46:12 EDT References: <171@ssc-vax.UUCP> <90@ncoast.UUCP> Organization: MIT, Cambridge, MA Lines: 20 !ncoast!bsafw states that he is in the process of starting a BBS on his system and doesn't want it confiscated... "... especially as a major local company depends on the system..." I would mention that it's probably a VERY BAD idea to do this. I hate to tell you, but a great deal of the traffic will be kids with TRS-80's that like to crack. Having them run on a system with potentially sensitive stuff on it (not to mention the fact that most people on this earth really suck when it comes to picking good passwords) is going to cause trouble. I would want any BBS I had to be responsible for to be physically disconnected from anything vital. BTW, some people have asked if I (I know, some of you out there think I'm a fascist, don't you?) would want to be responsible for everything coming out of my system? Well, I do. No, I don't read everything, but if something inappropriate does come out of this system, I will find the person responsible and take appropriate measures. This is a little easier to do when you do a real accountability-based system (like requiring names, addresses and affiliations (and an accountable sponsor) on paper. Due to their anarchic nature, BBS's can't really do this. -- Randwulf (Randy Haskins); Path= genrad!mit-eddie!rh