[Az-Geocaching] Revisiting caches over and over to get a TB?
Andrew Ayre
listserv@azgeocaching.com
Fri, 1 Aug 2003 13:40:47 -0700
This is a multi-part message in MIME format.
------=_NextPart_000_0016_01C35832.83AA48D0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
If I had a bug that was stuck in a cache that was not frequently visited, I
would probably appreciate the bug being removed by anyone to continue it's
journey. A posting of a note to the cache page will indicate at a minimum to
the cache owner that the cache is there still. Also there are some travel
bugs that are a game in itself, like the Wyle Operatives. I'm yet to be
convinced people taking the bug out of a cache causes anyone harm. I think
far more harmful are those who hold onto bugs for too long or who take them
but can't figure out how to record on the web site that they took them.
I tell you what IS dissapointing in my opinion. Finding a travel bug in
Rocky Point that wants to go to England. Asking the bug owner if they mind
me holding on to it for 2 months until I go over there. Taking it over there
in my hand luggage so the airline can't lose it. Waiting for the day I can
go caching to put it somewhere. Going out on the most awful English summer
day you can imagine to put it in a cache that is behind a mountain of sea
buckthorn that I had to wade through and get soaking wet. Then finding out
the cache was stolen along with the travel bug some time after our visit. :(
Andy
-----Original Message-----
From: az-geocaching-admin@listserv.azgeocaching.com
[mailto:az-geocaching-admin@listserv.azgeocaching.com]On Behalf Of
IFISHAZ@aol.com
Sent: Friday, August 01, 2003 1:22 PM
To: listserv@azgeocaching.com
Subject: [Az-Geocaching] Revisiting caches over and over to get a TB?
Ok, I could probably see that if the person was helping maintain the cache
it could be ok, but without naming names, I know of a couple of cachers who
do not help maintain the cache, doesn't even log on the cache page taking of
the bug (only logs to the bug page), makes no trades for the bug thus
lowering the inventory of the cache. Hense showing only an interest in
getting bugs out of the cache with not much concern for the cache or cache
owner. This is where I am having a problem seeing it as ok.
Once again just my opinion, IFISHAZ.
------=_NextPart_000_0016_01C35832.83AA48D0
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><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D324013420-01082003>If I=20
had a bug that was stuck in a cache that was not frequently visited, I =
would=20
probably appreciate the bug being removed by anyone to continue it's =
journey. A=20
posting of a note to the cache page will indicate at a minimum to the =
cache=20
owner that the cache is there still. Also there are some travel bugs =
that are a=20
game in itself, like the Wyle Operatives. I'm yet to be convinced people =
taking=20
the bug out of a cache causes anyone harm. I think far more harmful are =
those=20
who hold onto bugs for too long or who take them but can't figure out =
how to=20
record on the web site that they took them.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D324013420-01082003></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D324013420-01082003>I tell=20
you what IS dissapointing in my opinion. Finding a travel bug in Rocky =
Point=20
that wants to go to England. Asking the bug owner if they mind me =
holding on to=20
it for 2 months until I go over there. Taking it over there in my hand =
luggage=20
so the airline can't lose it. Waiting for the day I can go caching to =
put it=20
somewhere. Going out on the most awful English summer day you can =
imagine to put=20
it in a cache that is behind a mountain of sea buckthorn that I had to =
wade=20
through and get soaking wet. Then finding out the cache was stolen along =
with=20
the travel bug some time after our visit. :(</SPAN></FONT></DIV>
<P><FONT size=3D2>Andy<BR><BR></FONT></P>
<BLOCKQUOTE>
<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>IFISHAZ@aol.com<BR><B>Sent:</B> Friday, August 01, 2003 1:22=20
PM<BR><B>To:</B> listserv@azgeocaching.com<BR><B>Subject:</B> =
[Az-Geocaching]=20
Revisiting caches over and over to get a TB?<BR><BR></FONT></DIV><FONT =
face=3Darial,helvetica><FONT lang=3D0 face=3DArial size=3D2 =
FAMILY=3D"SANSSERIF">Ok, I=20
could probably see that if the person was helping maintain the cache =
it could=20
be ok, but without naming names, I know of a couple of cachers who do =
not help=20
maintain the cache, doesn't even log on the cache page taking of the =
bug (only=20
logs to the bug page), makes no trades for the bug thus lowering the =
inventory=20
of the cache. Hense showing only an interest in getting bugs out of =
the cache=20
with not much concern for the cache or cache owner. This is where I am =
having=20
a problem seeing it as ok.<BR>Once again just my opinion, =
IFISHAZ.</FONT>=20
</FONT></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0016_01C35832.83AA48D0--