Jump to content

Picked Up Tb


MissippiSlim

Recommended Posts

I'm new at this, was curious about something, so thought I'd ask.

 

My wife and I went by a cache today and were planning to grab the TB listed as being there. It was gone, but another was in its place; someone had logged both picking up the one we were expecting to find and dropping off a different one in the cache, logging both in the cache logbook with yesterday's date. We grabbed the one that was there.

 

Upon return, it doesn't show as being in the cache but still shows as being in someone else's possession (not so surprising, really, being only one day). So while I assume this one will show up 'any day now' as being dropped there yesterday, it made me curious as to how long you would normally wait prior to deciding a TB isn't going to be logged (which, I'm sure, happens from time to time). And once you decide that it isn't going to be logged, what's the process to get it showing up in your possession?

 

Thanks (and thanks to all who support such a neat hobby),

 

MissippiSlim

Link to comment

The guy seems to be from a bit further away from home. Maybe give him a few extra days. If possible, you could wait until the day before you plan to place the TB into its next cache. Just make sure it's in your online inventory when you hit the trail to place it, so you can post its next move properly.

 

The best procedure to get it into your possession is to grab it from whereever it is posted, log it into the cache where you found it so that the TB map will be accurate, then grab it again into your possession for your next move. The last two parts are optional, but it's an excellent courtesy for the TB owner to have all the stops on the map.

Link to comment

Give the other cacher lots of time. I've learned my lesson about trying to log a TB too quickly. We picked one up on the Applachian Trail while in PA for the weekend. When we got home we saw the TB still showed being carried by someone else. I waited a few days and I emailed them and the TB owner before I finally figured they must have forgotten so I grabbed it from them. About a week after that I got an email from them, they had taken a family vacation and had been out hiking the AT for about 2 weeks. I felt terrible. If I had only been more patient. They had some great pics to post which they were able to post in their first pick-up post, but they could not post a drop off since I grabbed it.

 

But I also learned another lesson too, if I drop off a TB and I know I will be away from a computer for a long time I will give that info in the cache log book. It still doesn't guarentee someone will see what I wrote, but if they look through the log they might.

Link to comment

I'll side with Team Red Oak on this one. Half the fun of travel bugs is logging them into their new location. Perhaps the wording should be changed from "If you can help this bug along, grab it" (or somesuch).

We went on a week's geocaching vacation across NJ, DE, MD, DC, WVa and Penna. We had no computer access during this trip. We dropped off five Bugs to help them on their travels. Three were grabbed before our return. One was grabbed within two hours of being dropped off! Well, that certainly spoiled my fun. I won't be taking any more bugs on vacation! I did grab them back, and log them into the caches, with a note to the grabber. One grabber told me that I was out of luck. Three days was the maximum time to wait. Thanks, dude. You certainly spoiled my fun. I won't be taking any more bugs on vacation.

 

Common courtesy would seem to say to permit enough time for the bug dropper to log the bug into the cache. A week would not be unusual. E-mail the bug holder after a few days. And again after a week. After two weeks with no response, I might consider grabbing the bug. Though common courtesy does seem to be lacking in this area of geocaching.

 

I vote for giving it time. Are you or the bug in that much of a hurry that you'd spoil someone's vacation?

Link to comment

Well sure, but sometimes there are situations. It would be nice if once we retrieve a bug we could wait until the last person finished the drop, but it's not always possible or reasonable. What happens when people find a bug, retrieve it and drop it into the next cache only to find when logging on line the last person hasn't made the drop. Now it's two caches off track.

 

It may seem like we're doing the last cacher a favor but really, it's the bug that can suffer. Sure some people might not have access to a computer for over a week, but is the next cacher and the next and the next supposed to wait until the missing cacher logs it?

 

There is no harm in grabbing it away after a resonable amount of time (three days) and dropping in the cache you found it in, retrieving it and dropping in the next cache. The last cacher has that bug found stat and the bug is recorded properly.

 

Nobody lost out on anything and the bug's true location isn't a big question mark.

Edited by BlueDeuce
Link to comment

Thanks for the (range of) replies, all good points. I've though that a vacation or business trip would be a good time to take a few TBs and get some mileage on them, but can see (particularly on a vacation) where it would be a few days before being able to log the bug (though there are many coffee shops that have web access these days).

 

I just wasn't sure if there was an established protocol or everyone just played it by ear. It appears to vary, and I'm sure my own version of the answer will evolve over time.

 

Thanks again,

 

MissippiSlim

Link to comment

It may seem like we're doing the last cacher a favor but really, it's the bug that can suffer. Sure some people might not have access to a computer for over a week, but is the next cacher and the next and the next supposed to wait until the missing cacher logs it?

 

A bug's mission should never be so critical that some patience can't be practiced. Sometimes 3 days should be plenty and other times 2-3 weeks seems like not enough time. You'll be able to best determine when that person had time to log the bug by carefully perusing the log at the cache, and then observe the last time that person logged into gc.com.

Link to comment

It may seem like we're doing the last cacher a favor but really, it's the bug that can suffer. Sure some people might not have access to a computer for over a week, but is the next cacher and the next and the next supposed to wait until the missing cacher logs it?

 

A bug's mission should never be so critical that some patience can't be practiced. Sometimes 3 days should be plenty and other times 2-3 weeks seems like not enough time. You'll be able to best determine when that person had time to log the bug by carefully perusing the log at the cache, and then observe the last time that person logged into gc.com.

Okay, you've retrieved a bug.....

 

You hold it for...whatever amount of time.....

 

You go on a trip, drop the bug, leave.

 

Now, explain to me what exactly you lose out on by someone grabbing the bug a way from you.

 

(oh sure, the bug should be dropped in the cache so it gets its miles. [God forbid that the point-to-point mileage isn't perfectly accurate]. Every cache it visits should be recorded).

 

ummmmmm, you lose out on getting to click it from your inventory. Sorry, that's all I can think that might be a problem.

Edited by BlueDeuce
Link to comment

I lose the satisfaction of logging the bug into the cache I moved it to. And being part of helping the bug along. And the desire to move bugs when on vacation.

The bug loses its continuity, it's travels. The bug I dropped in Maryland, and you grabbed and moved to Alabama lost its stop in Mayrland.

I've lost the fun of moving bugs any distance. And, big AND, I've lost the confidence that fellow cachers are interested in playing this game properly.

So, you go grab any and all bugs, with no consideration for other cachers. I'll only move bugs a short distance henceforth. You've ruined that part of the game for me.

Link to comment
I lose the satisfaction of logging the bug into the cache I moved it to.  And being part of helping the bug along.  And the desire to move bugs when on vacation.

The bug loses its continuity, it's travels.  The bug I dropped in Maryland, and you grabbed and moved to Alabama lost its stop in Mayrland.

I've lost the fun of moving bugs any distance.  And, big AND, I've lost the confidence that fellow cachers are interested in playing this game properly.

So, you go grab any and all bugs, with no consideration for other cachers.  I'll only move bugs a short distance henceforth.  You've ruined that part of the game for me.

 

nevermind

Edited by BlueDeuce
Link to comment

As I was saying, (in case you choose to ignore previous postings), you should wait at least three days, if you can wait longer, please do so.

 

However, there may be situations when you should grab a bug so that it is tracked properly. Fortunately the stats of the currect holder will show they grabbed the bug and the bug won't get lost in the suffle.

Edited by BlueDeuce
Link to comment

It may seem like we're doing the last cacher a favor but really, it's the bug that can suffer. Sure some people might not have access to a computer for over a week, but is the next cacher and the next and the next supposed to wait until the missing cacher logs it?

 

A bug's mission should never be so critical that some patience can't be practiced. Sometimes 3 days should be plenty and other times 2-3 weeks seems like not enough time. You'll be able to best determine when that person had time to log the bug by carefully perusing the log at the cache, and then observe the last time that person logged into gc.com.

Okay, you've retrieved a bug.....

 

You hold it for...whatever amount of time.....

 

You go on a trip, drop the bug, leave.

 

Now, explain to me what exactly you lose out on by someone grabbing the bug a way from you.

 

(oh sure, the bug should be dropped in the cache so it gets its miles. [God forbid that the point-to-point mileage isn't perfectly accurate]. Every cache it visits should be recorded).

 

ummmmmm, you lose out on getting to click it from your inventory. Sorry, that's all I can think that might be a problem.

That just shows how impatient you are and it was patience I was advocating and you ignore the fact I may have not been able to get to a computer yet to be able to log my adventures.

Edited by TotemLake
Link to comment
Guest
This topic is now closed to further replies.
×
×
  • Create New...