[Az-Geocaching] RE: Travel Bugs revisited

Koch, Dan listserv@azgeocaching.com
Thu, 14 Nov 2002 18:42:25 -0700


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C28C48.3FF63830
Content-Type: text/plain;
	charset="iso-8859-1"

I think that's the key...we all know that the information given about bugs
may not be current.  You have to figure that if at least one cacher has
visited the cache since the bug was put in it, then the bug is probably not
there anymore.  It isn't often that bugs are passed over for other trinkets.
You can't run to a cache specifically for the travelbug that is supposed to
be contained within, especially if it has 'been there' for a while.  
 
It's very similar to when a cache goes missing but hasn't been archived yet.
In the back of your mind, you know that every cache hunt could be a wild
goose chase but you still take your chances, especially if the cache hasn't
been found for a while.  It just happens much more often with travelbugs.
Knowing all the problems that are inherent in their 'being', we can't always
expect them to be where they say they are.  
 
I consider travelbugs to be a "luxury item", something that is nicer than
the standard junk that one finds in some (most?) caches.  They're a nice
surprise to find when you open up the container.  Sure, travelbugs have
their issues and many do get lost.  But I say just do your part and play by
the 'rules'.  Take them if you want them; just make sure to log them as
picked up and place them within a reasonable amount of time.  They're a fun
part of the 'game', but you can't focus on them...right CHUMP?
 
LazyK - Dan

-----Original Message-----
From: RAND HARDIN [mailto:RHrdn8@msn.com]
Sent: Thursday, November 14, 2002 5:58 PM
To: listserv@azgeocaching.com
Subject: Re: [Az-Geocaching] RE: Travel Bugs revisited (Ken Akerman)


One of my biggest gripes with Travel Bugs is when someone stops by a cache,
picks it up and doesn't add a note, the date, and the time in the log book
when they took it - then doesn't get to a computer to record the information
for several days.  How many of us have gone to a cache to pick up a TB only
to find it missing - and then watch the cache page for several days
wondering what happened to the bug?  I'm sure many of us have burned a lot
of gas chasing these missing TBs.
 
Rand  
 

----- Original Message -----
From: RAND HARDIN
Sent: Thursday, November 14, 2002 5:12 PM
To: listserv@azgeocaching.com
Subject: Re: [Az-Geocaching] RE: Travel Bugs revisited (Ken Akerman)
 
Ken, 
 
About the only way to solve this problem is not placing a Travel Bug in a
cache unless you know that you can get to a computer to log it within a
reasonable time.
 
Rand 
 

----- Original Message -----
From: ken@highpointer.com
Sent: Thursday, November 14, 2002 5:03 PM
To: az-geocaching@listserv.azgeocaching.com
Subject: [Az-Geocaching] RE: Travel Bugs revisited (Ken Akerman)
 

I wish there was a way to immediately log a cache finding and a travel bug
as soon as you find a cache.  When I travel, I like to find caches, and
particularly I like to move travel bugs that I find in caches near my home
to caches as far away as possible, to put more miles on them.  However, when
I am on the road I may not be able to get to a computer for several days.
This poses a problem for travel bugs, because someone may find the travel
bug before I get a chance to enter it at home or at the office. 


For example, while in Utah I put a travel bug in a cache, and while hiking
out I encountered the next group of local geocachers en route to the cache.
I told them about the travel bug that I had put in it, and they agreed not
to log their travel bug finding until I had a chance to enter the travel bug
when I got home, which was two days later.  However, if I had not
encountered those geocachers on the way out, they would have picked up the
travel bug and likely would have tried to enter it before I had a chance to
enter it at home. 


What can you do about delayed updates to travel bug logs, when you are on
the road and are away from computer access for several days or more?  This
appears to be a flaw in the travel bug system. 


Ken


------_=_NextPart_001_01C28C48.3FF63830
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 6.00.2719.2200" name=GENERATOR></HEAD>
<BODY 
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; FONT: 10pt verdana; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none">
<DIV><SPAN class=814442101-15112002><FONT face=verdana>I think that's the 
key...we all know that the information given about bugs may not be 
current.&nbsp; You have to figure that if at least one cacher has visited the 
cache since the bug was put in it, then the bug is probably not there 
anymore.&nbsp; It isn't often that bugs are passed over for other 
trinkets.&nbsp; You can't run to a cache specifically for the travelbug 
that&nbsp;is supposed to be&nbsp;contained within, especially if it has 'been 
there' for a while.&nbsp; </FONT></SPAN></DIV>
<DIV><SPAN class=814442101-15112002><FONT 
face=verdana></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=814442101-15112002><FONT face=verdana>It's very similar to when 
a cache goes missing but hasn't been archived yet.&nbsp; In the back of your 
mind, you know&nbsp;that every cache hunt could be a wild goose chase&nbsp;but 
you still take your chances, especially if the cache hasn't been found for a 
while.&nbsp; It just happens much more often with travelbugs.&nbsp; Knowing all 
the problems that are inherent in their 'being', we can't always&nbsp;expect 
them to be where they say they are.&nbsp; </FONT></SPAN></DIV>
<DIV><SPAN class=814442101-15112002></SPAN><SPAN class=814442101-15112002><FONT 
face=verdana></FONT></SPAN><SPAN class=814442101-15112002><FONT 
face=verdana></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=814442101-15112002><FONT face=verdana>I consider travelbugs to 
be a "luxury item", something that is nicer than the standard junk that one 
finds in&nbsp;some (most?) caches.&nbsp;&nbsp;They're a nice surprise to find 
when you open up the container.&nbsp; </FONT></SPAN><SPAN 
class=814442101-15112002><FONT face=verdana>Sure, travelbugs have their issues 
and many do get lost.&nbsp; But I say just do your part and play by the 
'rules'.&nbsp; Take them if you want them; just make sure to log them as picked 
up and place them&nbsp;within a reasonable amount of time.&nbsp; They're a fun 
part of the 'game', but you can't focus on them...right 
CHUMP?</FONT></SPAN></DIV>
<DIV><SPAN class=814442101-15112002><FONT 
face=verdana></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=814442101-15112002><FONT face=verdana>LazyK - 
Dan</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT 
  face=Tahoma>-----Original Message-----<BR><B>From:</B> RAND HARDIN 
  [mailto:RHrdn8@msn.com]<BR><B>Sent:</B> Thursday, November 14, 2002 5:58 
  PM<BR><B>To:</B> listserv@azgeocaching.com<BR><B>Subject:</B> Re: 
  [Az-Geocaching] RE: Travel Bugs revisited (Ken Akerman)<BR><BR></FONT></DIV>
  <DIV>One of my biggest gripes with Travel Bugs is when someone stops by a 
  cache, picks it&nbsp;up and&nbsp;doesn't&nbsp;add a note, the date, and the 
  time in the log book&nbsp;when they took it -&nbsp;then&nbsp;doesn't get to a 
  computer to&nbsp;record the information for several days.&nbsp; How many of us 
  have gone to a cache to pick up a TB only to find it missing - and then watch 
  the&nbsp;cache page for several days wondering what happened to the bug?&nbsp; 
  I'm sure many of&nbsp;us have burned a lot of gas chasing these missing 
  TBs.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Rand&nbsp;&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <BLOCKQUOTE 
  style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style="FONT: 10pt Arial">----- Original Message -----</DIV>
    <DIV 
    style="BACKGROUND: #e4e4e4; FONT: 10pt Arial; COLOR: black"><B>From:</B> 
    RAND HARDIN</DIV>
    <DIV style="FONT: 10pt Arial"><B>Sent:</B> Thursday, November 14, 2002 5:12 
    PM</DIV>
    <DIV style="FONT: 10pt Arial"><B>To:</B> listserv@azgeocaching.com</DIV>
    <DIV style="FONT: 10pt Arial"><B>Subject:</B> Re: [Az-Geocaching] RE: Travel 
    Bugs revisited (Ken Akerman)</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>Ken, </DIV>
    <DIV>&nbsp;</DIV>
    <DIV>About the only way to solve this problem is not placing a Travel Bug in 
    a cache unless you know that you can get to a computer to log it within a 
    reasonable time.</DIV>
    <DIV>&nbsp;</DIV>
    <DIV>Rand&nbsp;</DIV>
    <DIV>&nbsp;</DIV>
    <BLOCKQUOTE 
    style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
      <DIV style="FONT: 10pt Arial">----- Original Message -----</DIV>
      <DIV 
      style="BACKGROUND: #e4e4e4; FONT: 10pt Arial; COLOR: black"><B>From:</B> 
      ken@highpointer.com</DIV>
      <DIV style="FONT: 10pt Arial"><B>Sent:</B> Thursday, November 14, 2002 
      5:03 PM</DIV>
      <DIV style="FONT: 10pt Arial"><B>To:</B> 
      az-geocaching@listserv.azgeocaching.com</DIV>
      <DIV style="FONT: 10pt Arial"><B>Subject:</B> [Az-Geocaching] RE: Travel 
      Bugs revisited (Ken Akerman)</DIV>
      <DIV>&nbsp;</DIV>
      <P>I wish there was a way to immediately log a cache finding and a travel 
      bug as soon as you find a cache.&nbsp; When I travel, I like to find 
      caches, and particularly I like to move travel bugs that I find in caches 
      near my home to caches as far away as possible, to put more miles on 
      them.&nbsp; However, when I am on the road I may not be able to get to a 
      computer for several days.&nbsp; This poses a problem for travel bugs, 
      because someone may find the travel bug before I get a chance to enter it 
      at home or at the office. 
      <P>For example, while in Utah I put a travel bug in a cache, and while 
      hiking out I encountered the next group of local geocachers&nbsp;en route 
      to the cache.&nbsp; I told them about the travel bug that I had put in it, 
      and they agreed not to log their travel bug finding until I had a chance 
      to enter the travel bug when I got home, which was two days later.&nbsp; 
      However, if I had not encountered those geocachers on the way out, they 
      would have picked up the travel bug and likely would have tried to enter 
      it before I had a chance to enter it at home. 
      <P>What can you do about delayed updates to travel bug logs, when you are 
      on the road and are away from computer access for several days or 
      more?&nbsp; This appears to be a flaw in the travel bug system. 
      <P>Ken</P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C28C48.3FF63830--