[Az-Geocaching] Cache Pirate on the loose: Here is how I will protect my caches
Ken
listserv@azgeocaching.com
Sun, 4 May 2003 12:45:24 -0700
This is a multi-part message in MIME format.
------=_NextPart_000_0074_01C3123B.07D250A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MessageNo..most of my caches were placed before they implemented their =
policies. My "Black Cave" cache has recently been picked up by an =
unknown self appointed cache cop. According to this unknown person the =
cache was apparently near an archeological site. This was totally =
unknown to me when I placed the cache and they never made any attempt to =
contact me about the sensitive nature of the placement. Black Cave is =
clearly posted on TOPO maps of the region and there is a clear trail to =
the entrance. The cave is not a secret and again is publicly known from =
the posting on TOPO maps. The only way I found about the confiscation =
was from a cryptic note that was left by the person who took it. See =
GCA0E6 for more info.
Ken
----- Original Message -----=20
From: Bill Tomlinson=20
To: listserv@azgeocaching.com=20
Sent: Sunday, May 04, 2003 12:24 PM
Subject: RE: [Az-Geocaching] Cache Pirate on the loose: Here is how I =
will protect my caches
Ken,
Am I understanding correctly that you will be making your caches =
members only to avoid land managers and the policies they have in place?
CacheLess
-----Original Message-----
From: az-geocaching-admin@listserv.azgeocaching.com =
[mailto:az-geocaching-admin@listserv.azgeocaching.com] On Behalf Of Ken
Sent: Sunday, May 04, 2003 12:18 PM
To: listserv@azgeocaching.com
Subject: Re: [Az-Geocaching] Cache Pirate on the loose: Here is how =
I will protect my caches
I have decided to do the same. With all the land managers out =
grabbing my caches and now this bozo on the loose it is becoming to =
frustrating.
Ken
WhereRwee?
----- Original Message -----=20
From: Ken Akerman=20
To: listserv@azgeocaching.com=20
Sent: Sunday, May 04, 2003 11:33 AM
Subject: [Az-Geocaching] Cache Pirate on the loose: Here is how I =
will protect my caches
To Arizona Geocachers,
It's sad to see that there apparently is a cache pirate on the =
loose. I thought his entries were a joke, because he stated that he was =
at two caches on Saturday that I visited in the morning (neither one was =
plundered at that time), but when I checked the log for Pushing Tin near =
Sky Harbor International Airport, I read that Azcachmeister had visited =
the cache this morning and reported that it indeed had been plundered.
I am heading out to the Diamondbacks game in a short time, so on =
the way there I will stop at a cache that I visit frequently, Have Bug, =
Will Travel. I stopped there Saturday morning to get the only travel =
bug in it and I moved the travel bug to another cache in Pinal County =
later that day. Fortunately, if the pirate did clean out this cache, =
there were no travel bugs in it.
In order to protect my traditional caches, I have made them all =
Members Only. This is to protect my own caches from plundering, as it =
appears the Cache Pirate is not a Geocaching.com Premium Member. I =
recommend that all cachers make your caches Members Only (and become a =
Premium Member if you are not a member) now to protect them from =
plundering. (Virtual caches cannot be plundered, so those are open to =
all).
Since there are some new cachers who perhaps aren't sure if they =
want to pay the $30 annual fee to become a Premium Member, here is what =
I will do for you. If you want to find one of my Members Only caches, =
and you are not yet a Premium Member and have been an active geocacher =
for less than three months with fewer than 50 cache findings, then you =
could find one of my caches without becoming a Premium Member. To do =
this, send me an e-mail explaining what cache you would like to find, =
and I will respond with an e-mail listing the coordinates and a brief =
description. You could find the cache and sign the logbook in the =
cache, but you won't be able to log your finding on Geocaching.com until =
you become a Premium Member.
This is available to new geocachers only (and obviously does not =
apply to the Cache Pirate). I hope this new personal policy is =
agreeable to all, and in my opinion will encourage Geocachers to become =
Premium Members without restricting access to geocaching by newcomers.
Ken Akerman (a.k.a. Highpointer)
------=_NextPart_000_0074_01C3123B.07D250A0
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><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>No..most of my caches were placed =
before they=20
implemented their policies. My "Black Cave" cache has recently been =
picked up by=20
an unknown self appointed cache cop. According to this unknown person =
the cache=20
was apparently near an archeological site. This was totally unknown to =
me when I=20
placed the cache and they never made any attempt to contact me about the =
sensitive nature of the placement. Black Cave is clearly posted on TOPO =
maps of=20
the region and there is a clear trail to the entrance. The cave is not a =
secret=20
and again is publicly known from the posting on TOPO maps. The only way =
I found=20
about the confiscation was from a cryptic note that was left by the =
person who=20
took it. See <SPAN id=3DWaypointName><FONT =
face=3DVerdana>GCA0E6 for more=20
info.</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DVerdana size=3D2><SPAN></SPAN></FONT> </DIV>
<DIV><FONT face=3DVerdana size=3D2><SPAN>Ken</SPAN></FONT></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=3Dbilltomlinson@qwest.net =
href=3D"mailto:billtomlinson@qwest.net">Bill=20
Tomlinson</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> Sunday, May 04, 2003 =
12:24 PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [Az-Geocaching] =
Cache Pirate=20
on the loose: Here is how I will protect my caches</DIV>
<DIV><BR></DIV>
<DIV><SPAN class=3D666292319-04052003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Ken,</FONT></SPAN></DIV>
<DIV><SPAN class=3D666292319-04052003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D666292319-04052003><FONT face=3DArial =
color=3D#0000ff size=3D2>Am I=20
understanding correctly that you will be making your caches members =
only to=20
avoid land managers and the policies they have in =
place?</FONT></SPAN></DIV>
<DIV><SPAN class=3D666292319-04052003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D666292319-04052003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>CacheLess</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> <A =
=
href=3D"mailto:az-geocaching-admin@listserv.azgeocaching.com">az-geocachi=
ng-admin@listserv.azgeocaching.com</A>=20
[mailto:az-geocaching-admin@listserv.azgeocaching.com] <B>On Behalf =
Of=20
</B>Ken<BR><B>Sent:</B> Sunday, May 04, 2003 12:18 PM<BR><B>To:</B>=20
listserv@azgeocaching.com<BR><B>Subject:</B> Re: [Az-Geocaching] =
Cache=20
Pirate on the loose: Here is how I will protect my=20
caches<BR><BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I have decided to do the same. With =
all the=20
land managers out grabbing my caches and now this bozo on the loose =
it is=20
becoming to frustrating.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Ken</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>WhereRwee?</FONT></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 =
href=3D"mailto:ken@highpointer.com">Ken=20
Akerman</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
title=3Dlistserv@azgeocaching.com=20
=
href=3D"mailto:listserv@azgeocaching.com">listserv@azgeocaching.com</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Sunday, May 04, 2003 =
11:33=20
AM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Az-Geocaching] =
Cache Pirate=20
on the loose: Here is how I will protect my caches</DIV>
<DIV><BR></DIV>
<DIV>To Arizona Geocachers,</DIV>
<DIV><BR>It's sad to see that there apparently is a <A=20
=
href=3D"http://www.geocaching.com/profile/default.asp?A=3D121309">cache =
pirate=20
</A>on the loose. I thought his entries were a joke, because =
he=20
stated that he was at two caches on Saturday that I visited in the =
morning=20
(neither one was plundered at that time), but when I checked the =
log for=20
<A=20
=
href=3D"http://www.geocaching.com/seek/cache_details.aspx?ID=3D67154">Pus=
hing=20
Tin</A> near Sky Harbor International Airport, I read that <A=20
=
href=3D"http://www.geocaching.com/profile/default.asp?A=3D88519">Azcachme=
ister=20
</A>had visited the cache this morning and reported that it indeed =
had=20
been plundered.</DIV>
<DIV> </DIV>
<DIV>I am heading out to the Diamondbacks game in a short time, so =
on the=20
way there I will stop at a cache that I visit frequently, <A=20
=
href=3D"http://www.geocaching.com/seek/cache_details.aspx?ID=3D13581">Hav=
e=20
Bug, Will Travel</A>. I stopped there Saturday morning to =
get the=20
only travel bug in it and I moved the travel bug to another cache =
in Pinal=20
County later that day. Fortunately, if the pirate did clean =
out this=20
cache, there were no travel bugs in it.</DIV>
<DIV> </DIV>
<DIV>In order to protect my traditional caches, I have made them =
all=20
<STRONG>Members Only</STRONG>. This is to protect my own =
caches from=20
plundering, as it appears the Cache Pirate is not a Geocaching.com =
Premium=20
Member. I recommend that all cachers make your caches=20
<STRONG>Members Only</STRONG> (and become a <STRONG>Premium=20
Member</STRONG> if you are not a member) <U>now</U> to protect =
them from=20
plundering. (Virtual caches cannot be plundered, so those =
are open=20
to all).</DIV>
<DIV> </DIV>
<DIV>Since there are some new cachers who perhaps aren't sure if =
they want=20
to pay the $30 annual fee to become a Premium Member, =
here is=20
what I will do for you. If you want to find one of my =
Members Only=20
caches, and you are not yet a Premium Member and have been an =
active=20
geocacher for <U>less than three months</U> with <U>fewer than 50 =
cache=20
findings</U>, then you could find one of my caches without =
becoming a=20
Premium Member. To do this, send me an e-mail explaining =
what cache=20
you would like to find, and I will respond with an e-mail listing =
the=20
coordinates and a brief description. You could find the =
cache and=20
sign the logbook in the cache, but you won't be able to log your =
finding=20
on Geocaching.com until you become a Premium Member.</DIV>
<DIV> </DIV>
<DIV>This is available to new geocachers only (and obviously =
does not=20
apply to the Cache Pirate). I hope this new personal policy =
is=20
agreeable to all, and in my opinion will encourage Geocachers to =
become=20
Premium Members without restricting access to geocaching by=20
newcomers.</DIV>
<DIV> </DIV>
<DIV><STRONG><FONT size=3D3>Ken Akerman</FONT></STRONG> (a.k.a.=20
<STRONG><EM>Highpointer</EM></STRONG>)</DIV>
<DIV> </DIV>
=
<DIV> </DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0074_01C3123B.07D250A0--