rob3k

Just noticed that the feedback thread has been changed from "Planned" to the less forceful "Under Consideration"

Somebody asked about exempting small series of caches from this rule and Jeremy suggested they would need to be setup as a multicache. "We'll consider it, but it isn't likely since you can do that with a multicache." http://feedback.geocaching.com/geocaching/...e#reply_3343998

I'd hate to have a rule such as that outlined the OP actually implemented. "We won't ask you any silly questions about powertrails, if your new cache is at least 1.5 km (1 mile) away from any of your other caches posted within the past three months." I've placed caches in three different parks and in one of them I placed three within a mile of each other. I wouldn't consider it anything close to a power trail and having my hides in proximity makes maintenance easier. I doubt I'd fool with an artificial rule forcing me to dole them out one per 3 months. If that happens I'd just hide one of them, or maybe just list them on one of the alternate sites and wait forever between finds. What's wrong with being able to take a few mile walk and pick up a half dozen caches? Not that I don't enjoy longer hikes with fewer caches as well, or even hikes with no caches, but variety is the spice of life.

Agreed - It is suppose to allow for better problem solving and to get questions answered and yet very many issues and questions go unanswered for hours or days or even weeks. Most every topic here at least got some kind of response. I've noticed the same thing. There wasn't often much response from Groundspeak on the forums here but at least some fellow cachers would chime in.

Agree with this. But, I also wouldn't worry about publicly calling the guy out about it.

I was talking about this yesterday with my main caching partner. My thought was a cache where you can park within 20 feet (or at least clear view) of GZ. I have one where you can park at a trail head a few hundred feet walk along a wooded trail to the cache, but I decided that isn't P&G enough for me to use the attribute. http://geolex.locusprime.net/ defines it as: "A easy-to-find cache that you can get very close to by car."

I have thought about setting up a multi in the CYOA mold, might be a good fall project.

Is Field Puzzle not an attribute option when creating a pocket query? I don't see it there. I'd go with the round trip hike myself. But I'm sure this is an example of something different COs will handle differently.

One problem with automatically archiving a cache when it has been disabled for a set period of time is this would leave some hiders to simply not disable a missing cache. Our local reviewers are pretty good about scanning disabled caches (similar to what knowschad's reviewer does.) I've also noticed some cachers posting notes that their cache is missing and they'll get out to replace when they can rather than disabling. My assumption is that at least some of these hiders are doing that to avoid the reviewer sweep.

I'd still contact the seller and explain the situation. And you can still file a claim with PayPal if they won't help you out, but yes if the seller enters the DC number you'll most likely lose.

You can always just put "Congrats to xxx for the FTF!" in your log if you happen to log your finds for they day before the FTFer.

Be sure to 'like' the suggestion that virtuals are restored on the feedback site if you'd like to see them make a return. Can't miss it, it's the one with the highest count. http://feedback.geocaching.com/geocaching/ideas/popular

There are quite a few of these going in my area, but they all include something like this in their list of ground rules: "By way of clarification, there is no requirement besides the standard signing of the cache log to prevent you from logging this cache when found." I don't have a problem with them, but haven't participated in any of the series (besides finding them after the FTF) to this point.

I have brought an additional piece of swag or two to restock when I'm checking on one of my caches, but I don't make special restocking trips. I think any cache owners who make an effort to keep their caches well stocked are going above and beyond, which is great. But that doesn't make COs who don't do this lazy or disrespectful. Just my 2 cents.

I'll have to contact them. Best results by calling?

Try and not pop a vein, ok? Would you please get a life? I keep forgetting why I put you on my ignore list... (the only one, by the way)... but I get tempted... I wonder what you said...I take a peek... and I get another stupid Team Cotati post. When will I learn? I'll give it a try. Perhaps I'll go post something really clever about pinehurst. I'll believe that one when I see it. Thanks for quoting. I've been Rickrolled again! Shouldn't quotes from ignored users also be hidden? I think that is a MAGOR MAGOR bug!! This script might do you: http://userscripts.org/scripts/show/734 (Haven't used that script myself, but I do this on a different forum using a script I tweaked.)

Noticed a week ago that the back of my Colorado has a crack. It's in the black plastic piece that slides off the unit. It's not cracked all the way through to inside any of the rubber gaskets so I expect it is still waterproof, but I don't plan to test that out. Probably only a matter of time until it splits completely apart and I'll have to duct tape it together. Anyone have something I can use to attempt to stop the bleeding? The battery cover has a vertical crack running directly up from the mounting spine.

I loved this type of hide the first time I encountered it. Cache description was funny talking about how the film canister was incredibly well camouflaged and nearly perfectly blended into it's surroundings. Left me wondering just what the CO crafted. Then I found an ammo can filled with film canisters. And they all had a roll of paper (so you couldn't just shake it and toss aside) with all but one printed up with a message like "Nope!" I was laughing for nearly half the time it took me to find the right container. Nah, I did get a big kick out of it. I think this can be a fun hide, but an area really only needs one such hide as you kind of see it once and then you don't really need to see it again.

Loved the site, thanks for keeping keeping it running as long as you did.

So, has anyone used this trail to bag 1000 in a day? Some reported find rates seem to point to this as a possibility.

You can't remove them from your personal stats without deleting the logs. As others mentioned they will drop off the display after 30 days. If you were a premium member using boookmark lists would be a good way to keep track. Actually on the drill down page you see all of your DNF logs. Or, at least for me they go back to the first DNF I posted on my first day of caching. Link: http://www.geocaching.com/my/logs.aspx?s=1&lt=3 Would be pretty cool to have the red checkmark next to ones you subsequently found, but seems like a very unlikely enhancement to get implemented.

gotta agree. they already know all they need to know about you. i'd go get the cache and use this experience to educate them about caching. I'm not sure I understand how they would know exactly who the CO is and where to find him just from the geocache and the information on geocaching.com. Probably because I (and I think all cachers should) have their contact info on or in the cache. All of mine have my email address, all but one also have my name and phone number asking anyone with issues to contact me. If he put his phone number on or in the cache, then yes that would do it, but we don't really know that one way or the other. I would lean towards assuming he didn't do this or the detective would likely have phoned him up instead of sending an e-mail. But either way it's just an assumption. My guess would be the majority of caches I find do not include the hider's phone number or real name. Many do include the GC number, geocache name, and the hider's geocaching id. Not saying the CO should fear the police here, just curious why the assumption the police would already have all the info they need to make an ID in this instance.

gotta agree. they already know all they need to know about you. i'd go get the cache and use this experience to educate them about caching. I'm not sure I understand how they would know exactly who the CO is and where to find him just from the geocache and the information on geocaching.com.

Sounds like a candidate for a greasemonkey script.

I'd just ignore it unless the new cacher asked for advice in an e-mail to me or a forum post on the local caching group's site. Most likely I wouldn't worry about it even if it was on one of my caches.