Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 5/3/83; site intelca.UUCP Path: utzoo!linus!vaxine!wjh12!genrad!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!hplabs!intelca!glen From: glen@intelca.UUCP Newsgroups: net.micro Subject: Re: BBS Confiscated, a way to avoid it! Message-ID: <283@intelca.UUCP> Date: Thu, 31-May-84 13:24:14 EDT Article-I.D.: intelca.283 Posted: Thu May 31 13:24:14 1984 Date-Received: Wed, 6-Jun-84 02:28:03 EDT Organization: Intel, Santa Clara, Ca. Lines: 29 In college we had an operating system on one computer that scanned all terminal I/O for cuss words. If it found one, it would warn you not to use such language. If it found a second, it would warn you that one more occurrence and you would be logged out and your password changed. If it found a third, it would log you out and change your password thus forcing you into an embarrassing discussion with your TA to get your account back. Why couldn't a similar program be constructed for bulletin boards? It could scan for suspicious words. If it found any, it could either: warn the person about his messages of suspicious nature or better yet, not warn the person, but instead save the messages in some protected area where they can only be read by the sysop. Then they could be broadcast only after the sysop has read them and determined they were suitable. The list of suspicious words could be kept in an easily updatable dictionary. Granted, this solution isn't perfect as devious users could avoid such lingo with careful wording/misspelling, but atleast it's a step. Maybe someday an artificial intelligence program could figure out if the MEANING and not just the wording was appropriate for BBS's. ^ ^ Glen Shires, Intel, Santa Clara, Ca. O O Usenet: {ucbvax!amd70,pur-ee,hplabs}!intelca!glen > ARPA: "amd70!intelca!glen"@BERKELEY \-/ --- stay mellow