[Az-Geocaching] Obscenity written in log sheet of Mat274 cache on ASU campus
Brian LaFrance
listserv@azgeocaching.com
Sat, 26 Apr 2003 17:59:52 -0700
This is a multi-part message in MIME format.
------=_NextPart_000_000C_01C30C1D.A31122E0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
I beg to differ on the travel bug issue. Your argument is the same argument
that people use when joining health clubs. Just because they pay the fee
every month for the health club doesn't mean they are more responsible about
going and using that membership. I consider myself to be an addicted
cacher, but I sometimes am unable to put travel bugs into different caches
for a few weeks at a time. This is because I cannot revolve my life around
getting that travel bug into a cache, and I do not feel comfortable leaving
it in an urban cache...even if it is Members Only. As cachers using public
areas, we have to accept the fact that people will destroy caches. Many
times people probably come across them by accident or see people put them
back and decide to destroy them. A members only cache would not solve this
problem. I understand that some people feel that they like having their
caches be members only, but I would prefer to let all cachers enjoy the
sport equally. People who place members only caches are not helping the
game. When I started 6 months ago, it pissed me off that there were caches
out there that I couldn't view because I didn't pay for a membership. I
have supported Geocaching just as much or more than many members have
through my purchases from Geocaching.com and it's affiliations. I agree
that there should be limitations to the features on Geocaching.com for
people that are not members, but Geocaching is about the caches and they
should not be restricted to be accessed by a small number of people.
Brian
Team LeapLab
-----Original Message-----
From: az-geocaching-admin@listserv.azgeocaching.com
[mailto:az-geocaching-admin@listserv.azgeocaching.com]On Behalf Of
ken@highpointer.com
Sent: Saturday, April 26, 2003 4:50 PM
To: listserv@azgeocaching.com
Subject: [Az-Geocaching] Obscenity written in log sheet of Mat274 cache on
ASU campus
Geocachers,
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_000C_01C30C1D.A31122E0
Content-Type: text/html;
charset="us-ascii"
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=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D076374600-27042003><FONT face=3DArial color=3D#0000ff =
size=3D2>I beg=20
to differ on the travel bug issue. Your argument is the same =
argument that=20
people use when joining health clubs. Just because they pay the =
fee every=20
month for the health club doesn't mean they are more responsible about =
going and=20
using that membership. I consider myself to be an addicted cacher, =
but I=20
sometimes am unable to put travel bugs into different caches for a few =
weeks at=20
a time. This is because I cannot revolve my life around getting =
that=20
travel bug into a cache, and I do not feel comfortable leaving it in an =
urban=20
cache...even if it is Members Only. As cachers using public areas, =
we have=20
to accept the fact that people will destroy caches. Many times =
people=20
probably come across them by accident or see people put them back and =
decide to=20
destroy them. A members only cache would not solve this =
problem. I=20
understand that some people feel that they like having their caches be =
members=20
only, but I would prefer to let all cachers enjoy the sport =
equally. =20
People who place members only caches are not helping the game. =
When I=20
started 6 months ago, it pissed me off that there were caches out there =
that I=20
couldn't view because I didn't pay for a membership. I have =
supported=20
Geocaching just as much or more than many members have through my =
purchases from=20
Geocaching.com and it's affiliations. I agree that there should be =
limitations to the features on Geocaching.com for people that are =
not=20
members, but Geocaching is about the caches and they should not be =
restricted to=20
be accessed by a small number of people. </FONT></SPAN></DIV>
<DIV><SPAN class=3D076374600-27042003><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D076374600-27042003><FONT face=3DArial color=3D#0000ff =
size=3D2>Brian</FONT></SPAN></DIV>
<DIV><SPAN class=3D076374600-27042003><FONT face=3DArial color=3D#0000ff =
size=3D2>Team=20
LeapLab</FONT></SPAN></DIV>
<DIV><SPAN class=3D076374600-27042003></SPAN> </DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B>=20
az-geocaching-admin@listserv.azgeocaching.com=20
[mailto:az-geocaching-admin@listserv.azgeocaching.com]<B>On Behalf Of=20
</B>ken@highpointer.com<BR><B>Sent:</B> Saturday, April 26, 2003 4:50=20
PM<BR><B>To:</B> listserv@azgeocaching.com<BR><B>Subject:</B> =
[Az-Geocaching]=20
Obscenity written in log sheet of Mat274 cache on ASU=20
campus<BR><BR></FONT></DIV>
<DIV>Geocachers, </DIV>
<DIV> </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. 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. He wrote, "F*** this cache" instead of his name. =
This is=20
particularly disconcerting because the first person who recovered the =
cache=20
was Casey's 12-year old daughter, Sarah.</DIV>
<DIV> </DIV>
<DIV>What could we do about geocachers who do something like =
this? 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>". 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 fee (less than a tank of gas) to become a Premium =
Member.</DIV>
<DIV> </DIV>
<DIV>Protecting caches by making them "Members Only" will also reduce =
the risk=20
of lost travel bugs. Apparently the travel bug that =
RandMan put in=20
the cache was taken, but has not been logged yet. 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. =
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> </DIV>
<DIV><STRONG>Ken Akerman</STRONG> (a.k.a.=20
=
<STRONG><EM>Highpointer</EM></STRONG>)</DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_000C_01C30C1D.A31122E0--