[Az-Geocaching] Obscenity written in log sheet of Mat274 cache on ASU campus

Regan Smith listserv@azgeocaching.com
Sat, 26 Apr 2003 21:31:40 -0700


This is a multi-part message in MIME format.

------=_NextPart_000_0018_01C30C3B.39C01800
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

KEN=20
not all people who find a cache are GEOCACHERS Caches are found for many =
reasons who's to say that someone didn't notice a cacher looking for a =
cache and instead of asking what they were looking for or doing did find =
the cache themselves?=20

You must agree that to a non cacher when they see someone wonder around =
like cachers sometimes do it will draw attention. think about what you =
wrote in your log about say the end of the road cache, had you not =
talked to the fishermen, and not found the cache they could have just as =
well found it and taken it, but as it turned out they helped... or even =
with MA274 cache you were there looking a time prior who noticed you?? =
did you notice everyone looking at you while you were searching???? or =
with the caches on South Mountain how many logs say HAD TO WAIT FOR =
PEOPLE TO WALK BY or such? what if a new cacher was to find the cache =
and not take the care to be stealth??? but then again if someone was to =
be stealth wouldn't that draw attention? as the news with all those =
alerts say look for suspicious activity......


  ----- Original Message -----=20
  From: ken@highpointer.com=20
  To: listserv@azgeocaching.com=20
  Sent: Saturday, April 26, 2003 4:50 PM
  Subject: [Az-Geocaching] Obscenity written in log sheet of Mat274 =
cache on ASU campus


  Geocachers,=20

  I was at Mat274 geocache on the ASU campus today, and I found it along =
with Casey and Sarah of AZCelts.  However, I was appalled when I opened =
the log sheet and saw that the previous finder had written an obscenity =
in the place for his name.  He wrote, "F*** this cache" instead of his =
name.  This is particularly disconcerting because the first person who =
recovered the cache was Casey's 12-year old daughter, Sarah.

  What could we do about geocachers who do something like this?  My idea =
(admittedly controversial, and something discussed before) is that all =
caches in public places like this should be "Members Only".  I expect =
that the kind of person who would write an obscenity in the log sheet =
would be less likely to pay the nominal annual fee (less than a tank of =
gas) to become a Premium Member.

  Protecting caches by making them "Members Only" will also reduce the =
risk of lost travel bugs.   Apparently the travel bug that RandMan put =
in the cache was taken, but has not been logged yet.  Many travel bugs =
become lost because they are taken by a geocacher who fails to log them =
properly and does not put the travel bug in another cache.   If a travel =
bug is placed in a "Members Only" cache, then it is more likely that the =
travel bug will be recovered by someone who will log the travel bug =
properly, and will put the travel bug promptly in another cache.

  Ken Akerman (a.k.a. Highpointer)
------=_NextPart_000_0018_01C30C3B.39C01800
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>KEN </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>not all people who find a cache are =
GEOCACHERS=20
Caches are found for many reasons who's to say that someone didn't =
notice&nbsp;a=20
cacher&nbsp;looking for a cache and instead of asking what they were =
looking for=20
or doing did find the cache themselves? </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>You must agree that to a non cacher =
when they see=20
someone wonder around like cachers sometimes do it will draw attention. =
think=20
about what you wrote in your log about say the end of the road cache, =
had you=20
not talked to the fishermen, and not found the cache they could have =
just as=20
well found it and taken it, but as it turned out they helped... or even =
with=20
MA274 cache you were there looking a time prior who noticed you?? did =
you notice=20
everyone looking at you while you were searching???? or with the caches =
on South=20
Mountain how many logs say HAD TO WAIT FOR PEOPLE TO WALK BY or such? =
what if a=20
new cacher was to find the cache and not take the care to be stealth??? =
but then=20
again if someone was to be stealth wouldn't that draw attention? as the =
news=20
with all those alerts say look for suspicious =
activity......</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dken@highpointer.com=20
  href=3D"mailto:ken@highpointer.com">ken@highpointer.com</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dlistserv@azgeocaching.com=20
  =
href=3D"mailto:listserv@azgeocaching.com">listserv@azgeocaching.com</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Saturday, April 26, 2003 =
4:50=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Az-Geocaching] =
Obscenity=20
  written in log sheet of Mat274 cache on ASU campus</DIV>
  <DIV><BR></DIV>
  <DIV>Geocachers, </DIV>
  <DIV>&nbsp;</DIV>
  <DIV>I was at <A=20
  =
href=3D"http://www.geocaching.com/seek/cache_details.aspx?ID=3D65700">Mat=
274=20
  </A>geocache on the ASU campus today, and I found it along with Casey =
and=20
  Sarah of AZCelts.&nbsp; However, I was appalled when I opened the log =
sheet=20
  and saw that the previous finder had written an obscenity in the place =
for his=20
  name.&nbsp; He wrote, "F*** this cache" instead of his name.&nbsp; =
This is=20
  particularly disconcerting because the first person who recovered the =
cache=20
  was Casey's 12-year old daughter, Sarah.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>What could we do about geocachers who do something like =
this?&nbsp; My=20
  idea (admittedly controversial, and something discussed before) is =
that all=20
  caches in public places like this should be "<STRONG>Members=20
  Only</STRONG>".&nbsp;&nbsp;I expect that the kind of person who would =
write an=20
  obscenity in the log sheet would be less likely to pay the nominal=20
  annual&nbsp;fee (less than a tank of gas) to become a Premium =
Member.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Protecting caches by making them "Members Only" will also reduce =
the risk=20
  of lost travel bugs.&nbsp;&nbsp; Apparently the travel bug that =
RandMan put in=20
  the cache was taken, but has not been logged yet.&nbsp; Many travel =
bugs=20
  become lost because they are taken by a geocacher who fails to log =
them=20
  properly and does not put the travel bug in another cache.&nbsp;&nbsp; =
If a=20
  travel bug is placed in a "Members Only" cache, then it is more likely =
that=20
  the travel bug will be recovered by someone who will log the travel =
bug=20
  properly, and will put the travel bug promptly in another cache.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV><STRONG>Ken Akerman</STRONG> (a.k.a.=20
  =
<STRONG><EM>Highpointer</EM></STRONG>)</DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0018_01C30C3B.39C01800--