Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!ittatc!dcdwest!sdcsvax!sdcc6!sdcc7!ln63soi
From: ln63soi@sdcc7.UUCP (ANTHONY INTRIERI)
Newsgroups: net.news.stargate,net.legal
Subject: Re: stargate liability issues
Message-ID: <338@sdcc7.UUCP>
Date: Thu, 24-Apr-86 06:24:31 EST
Article-I.D.: sdcc7.338
Posted: Thu Apr 24 06:24:31 1986
Date-Received: Fri, 25-Apr-86 03:20:18 EST
References: <2054@hao.UUCP> <334@ius2.cs.cmu.edu>
Reply-To: ln63soi@sdcc7.UUCP (ANTHONY INTRIERI)
Distribution: na
Organization: U.C. San Diego, Academic Computer Center
Lines: 16
Xref: dcdwest net.news.stargate:210 net.legal:2925

In article <2054@hao.UUCP> era@hao writes:
>My questions are:
>
>
>   Is there any technical solution, e.g. message body encryption, which
>   can get around the legalities?  Certain broadcasters... have used
>   scrambling ... which appears to be a method of legally transforming a 
>   broadcast channel into a common carrier.

If its just 4 letter words you're worried about, a pattern matching front end
would work.  Just grep for offensive words and turn them into stuff like:
sh*t, f--k, or even ****.  Other liability issues would be difficult to 
detect.  Maybe you could put in disclaimers like:  "the writer of this
message is solely responsible for it's content..."

Paul van de Graaf	U. C. San Diego