X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fbb9d,f70477391f4d86a6
X-Google-Attributes: gidfbb9d,public
X-Google-ArrivalTime: 1994-06-15 12:02:51 PST
Path: 
 nntp.gmd.de!xlink.net!howland.reston.ans.net!europa.eng.gtefsd.com!sundog.tiac.net!news.sprintlink.net!sashimi.wwa.com!gagme.wwa.com!not-for-mail
From: boba@gagme.wwa.com (Bob Allison)
Newsgroups: rec.arts.ascii
Subject: Talk: rot13 and ASCII art
Date: 15 Jun 1994 13:46:07 -0500
Organization: The University of Memphis
Lines: 35
Approved: boba@gagme.wwa.com
Distribution: world
Message-ID: <2tni9f$422@gagme.wwa.com>
References: <2tlmrh$ui@gagme.wwa.com> <2tn6r3$qap@gagme.wwa.com>
NNTP-Posting-Host: gagme.wwa.com
Summary: rot13 protection



In article <2tn6r3$qap@gagme.wwa.com>, cmice@mke.ab.com (Christopher =
Ice x2136) writes:
> In the future, you can "Rot13" your posts if you feel it is somethi=
ng which
> may offend some people.  Then the reader has to deliberately un-Rot=
13 it...in
> which case, they were duly warned.  I think the ^L was pretty effec=
tive in any
> case, but school teachers or parents with internet access for kids =
can remove
> the ability to un-Rot13, and to some extent, have control over what=
 their kids=20
> see

Good suggestion, but is won't work.  I went and look at the post Rot1=
3 and you
could still definately make out what it was.  Rot13 just basically ch=
anges
letters around so you could not read what was said but you can tell w=
hat the
picture is.  I guess the best think to do is to make sure there is pr=
oper
warning in the header and do ^L or blank screens with more warnings.
--=20
                    Keep a cool and  _\|/_  Have a good Weekend!   =
=20
                                     {=EE =EE}    =20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DooO=3D(_)=3DOoo=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D