+fehrgo Posted November 17, 2006 Share Posted November 17, 2006 I've looked around, but can't find any protocol for this. What do you do when a well meaning, short time cacher posts the tracking number for a bug of yours in their cache log entry, but then does not respond nor act when you request that they remove it? The owner of the cache in question has also not been responsive on the issue, so I'm trying to figure out what the next level to take it to would be. Any help is greatly appreciated! Quote Link to comment
+SUp3rFM & Cruella Posted November 17, 2006 Share Posted November 17, 2006 If the geocacher or the owner don't answer your mails, there's nothing you can do... Except, paying attention to your TB, looking out for bogus discovery logs. If you suspect of a bogus log on your tb, contact them and try to find out if the logger really saw it. Quote Link to comment
Not So Lost Puppies Posted November 17, 2006 Share Posted November 17, 2006 I believe I've seen where the administrators or moderators have been able to fix such things if the others will not respond. Quote Link to comment
+The Leprechauns Posted November 17, 2006 Share Posted November 17, 2006 Yep. Write to your friendly volunteer cache reviewer and they will be happy to edit the log if you say that efforts to get the log owner to do it have been unsuccessful. Or if your reviewer is too busy, or you don't know who to write to, then Eartha will be glad to help. Quote Link to comment
+fehrgo Posted November 17, 2006 Author Share Posted November 17, 2006 Many thanks to all who replied! I'll go work on getting this taken care of again. Eric Quote Link to comment
+Eartha Posted November 17, 2006 Share Posted November 17, 2006 Just click on the blue PM button under my avatar to send me a message, tell me which bug it is, and I'll be happy to help. If you can link to the log, that's even better. In the meantime, if anyone posts a bogus log, you can delete it. Quote Link to comment
+fehrgo Posted November 18, 2006 Author Share Posted November 18, 2006 Thanks all for the help, theUMP cleaned up the log entry for me. Now my bug won't mysteriously be heading to polar caches! Quote Link to comment
+encece Posted November 24, 2006 Share Posted November 24, 2006 Explain this to me as I'm unsure what the concern is... I am a newbie and I recently made the mistake listed above. I understand that I'm not supposed to write the TB number on logs...but I cont really understand why. Could you explain that to me please. PS....was it me and a canadian geocoin? Quote Link to comment
+DiS02 Posted November 24, 2006 Share Posted November 24, 2006 Uhh, I thought it was the number on the geocoin or TB tag that shouldnt be posted but the one that starts out TB could be posted? As in TBxx123 could be posted but ABC789 (number on the coin) couldnt be. If I have it mixed up then I need to fix a post I made a couple days ago. Quote Link to comment
+BlueDeuce Posted November 24, 2006 Share Posted November 24, 2006 Explain this to me as I'm unsure what the concern is... I am a newbie and I recently made the mistake listed above. I understand that I'm not supposed to write the TB number on logs...but I cont really understand why. Could you explain that to me please. PS....was it me and a canadian geocoin? There are people who don't play nice and if you post the tracking number they might retrieve the bug on line without actually visiting the cache. It does happen. Each bug page provides a 'number' you can use to post: e.g. Use TBKPAZ to reference this item. Quote Link to comment
+encece Posted November 24, 2006 Share Posted November 24, 2006 Ah...I never think of what the bad guys could do. That's going to get me in trouble one day. Quote Link to comment
+welch Posted November 24, 2006 Share Posted November 24, 2006 Uhh, I thought it was the number on the geocoin or TB tag that shouldnt be posted but the one that starts out TB could be posted? As in TBxx123 could be posted but ABC789 (number on the coin) couldnt be. If I have it mixed up then I need to fix a post I made a couple days ago. No you have it right, the reference number thats given on the online page like "Use TBGF0Q to reference this item" can be posted, since that number can be used to find the TB page but not to actually log it found / discovered. However, the number thats actually on the coin or TB tag should not be posted as it does allow others to find/discover the item... and thus do things like BlueDeuce said. Quote Link to comment
+K0BKL Posted November 24, 2006 Share Posted November 24, 2006 I have found and moved Indian Star TB TBNGXM from one of my caches to another, but the site does not show my possession of it, even though I logged it as having discovered it. It was not logged into the cache where I found it. Owner's mail bounces. The TB is currently in Maple Hill GCH0NF Quote Link to comment
+BlueDeuce Posted November 24, 2006 Share Posted November 24, 2006 I have found and moved Indian Star TB TBNGXM from one of my caches to another, but the site does not show my possession of it, even though I logged it as having discovered it. It was not logged into the cache where I found it. Owner's mail bounces. The TB is currently in Maple Hill GCH0NF You've only logged it as 'Discovered'. The current cacher hasn't logged the drop, but I am assuming they signed your cache log. If it's been more than three days you should 'Grab' the bug from the current holder, post a note on your cache page to drop it (for tracking mileage), retrieve the bug, then drop it into the cache you left it in. Quote Link to comment
+DiS02 Posted November 26, 2006 Share Posted November 26, 2006 Thanks Welch & BlueDeuce, I thought I had done it right but then I had a 'turkey' moment so wanted to make sure. Yeah, I posted the TB #'s, not the ahh serial number on the items so they are good to go. No virt logging on my watch, heheh. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.