The A-Team

Nope. It doesn't matter what you use to dig with, it isn't allowed. Some cachers have used the wording of the guideline as a loophole to allow them to use their hands, but it has been clarified in the past that the spirit of the guideline is "no digging". Basically, if you are creating a hole in the ground in which to hide the cache, it isn't allowed. Face it, your hands are kind of pointy!

In the App, do the following: -Tap the "Menu" button at the very top -Tap "Settings" -Scroll down to the "Serach Options" section, and tap on "My Finds" -Tap "Exclude My Finds" -Tap "Close" at the very top Your finds will no longer come up in any searches. As far as "identifying", if you leave the above setting on "Include My Finds", your finds will show with a checkmark on the cache symbol in list view, and with a smiley in map view.

Not really a known problem, but rather an intended and partially-implemented feature. Groundspeak is gradually rolling out the "corrected coordinates" feature, and at this time it will only display in the corrected location on the cache page's minimap (the one at the end of the description). In a future site update, they'll turn on the functionality to have them show in the corrected position on the Beta Maps.

Like Dgwphotos, my original caching name was just my first initial and last name, and not very creative. Years ago, in a workplace hockey pool, I named my team "The A-Team", because my first name starts with 'A'. When I decided I wanted to change my caching name, I was lucky enough to find that "The A-Team" was in use by an "unvalidated" account, so GS allowed me to take the name. It opens up many additional benefits, such as having Mr. T as my avatar with the caption "I pity the fool that doesn't cache!". I've also started using the phrase "I love it when a plan comes together!" in my FTF logs, and I've considered using some kind of A-Team theme for some cache placements.

"The requested bookmark does not exist." That's good to know, though. I had no idea the moving caches were omitted.

And Groundspeak’s Geocaching for Android App, Groundspeak’s Geocaching for iPhone App, and Groundspeak’s Geocaching for Windows Phone 7 App. In her post in each new forum, Sandy danced around one word without actually saying it. It sums up what these new boards are for, and should be added to the front of each sub-forum title. What's the word? Support.

I have the feeling that most of those linked events were simple mistakes. On a couple of them, I had to re-read it several times to find the mention of a charity buried deep in the middle. For all we know, the reviewers in those areas are overworked, and simply don't have the time to dissect every word of every event listing that comes by.

Goals: -Fill in the calendar, or failing that, at least make a find on Feb 29. -Find at least some of the many boat-required caches in my area. -Reach 50 FTFs (unless I manage to get one in the next 10 days; I'm at 49 now) -Find the only benchmark in the region that's actually in Canada I'm also looking forward to participating in the organization of and attending BC's first Mega (GC349MK), only 45.9 km from home. It will be my 3rd Mega.

But on the plus side, they aren't pixelated!

You're right, it would have to be made very clear that it is only for serious problems, and that minor issues like a wet log should be logged with a NM. It really depends on what type of issue is reported. They may archive it, disable it, or simply contact the owner. That's an interesting question. The intention of this was to notify the reviewer, but can anyone think of any pros or cons to the CO also receiving such a notification? Obviously, the notification to the CO wouldn't contain the reporting user's name. I'm inclined to do it the other way around. Start out with the "other" category, and look at what people are using it for. After a while, it will become apparent if there is a need for some new categories. I think there's really a finite number of reasons to report a cache, so there should be categories suitable to catch all of them. Leaving an "other" category invites the earlier mentioned "bogus" reports.

I disagree. Mingo is not in the same category as the Project APE cache. That cache was a special type, and the significance was the original container. Mingo is a Traditional cache, and should be treated the same as any other Traditional. The original Mingo container is long gone, so by your reckoning, should have been archived already. If the container for one of your Traditional caches goes missing, do you automatically archive it, or do you replace it? Mingo is no different. Realistically, however, there are some logistical issues that need to be factored in by the owner, that aren't normally experienced by other Traditionals. Mingo can not realistically be replaced with a nano or a micro. The log would be full in less than a month. Due to the amount of traffic Mingo receives because it happens to be the oldest, it needs to be large enough to hold an adequately sized log, and have room for the inevitable large number of trackables. Unfortunately, there seems to be someone who doesn't want Mingo to exist. If the owner is willing to keep replacing it, then that's their choice, and Mingo will continue. If they get tired of replacing it, they can decide to archive it. That is their choice as the owner, and there's no reason why the geocaching community should have any say in the matter.

I like this idea. There are many cases where a cache should be archived, or at least brought to the attention of a reviewer, but cachers are unwilling to post a NA and be seen as a whistleblower. If you force the "reporter" to choose from several categories (ie. Permission issue, Guideline violation, Cache missing and owner inactive, etc.), and require a detailed explanation of why they are reporting it, you probably won't see too many bogus reports. Even when there are bogus reports, it should be pretty easy to tell. +1

Agreed. My personal take is that logging an adopted-out cache would, in general, be bad form. The one case where I could see it being OK would be if the new owner were to change how and where the cache is hidden. If it's still hidden how and where you originally hid it, though, I wouldn't log it.

In the GPS Reviews section, you can choose a manufacturer and then sort based on various criteria. I've found that 3 of the sort orders are sorting incorrectly. -"Most rated" actually sorts by "Highest rated" -"Most owned" actually sorts by "Highest rated" -"Release date" actually sorts by "Name (Z-A)"

I'd like to throw my support behind this. Yet again, we've had a new cacher submit and enable a cache before placing the container. Until the full revamp is complete, can you at least revise the text on the "Enable" tick box to mention something like "all parts of this geocache are in place and ready to be found"?

there is? Yeah, I'm confused too. The only option I can see that relates to a month is the "Placed during...the last month". That has nothing to do with how often the PQ will run, though.

"Your Stuff"? There's no such menu on Geocaching.com, and never has been. From the little GC box on the right side of your menubar, I have to assume you're using Greasemonkey, which probably explains why you and knowschad are seeing something different.

Already covered here: SUBMITTED (24998) - [FEATURE] add "Part of a powertrail" to cache attributes

meh, its been like that since last update Not for me. The "Play" menu was the first from the left after the last update, for me. The menus were reordered during the Dec 6th update, and some of us commented on it at that time: GOF and Bacall Myself I keep finding my mouse pointer heading toward the first menu, before remembering and veering off to the 3rd tab.

I think what happened is that you swapped the coordinates for the cache and the 1st stage. The coordinates provided for the 1st stage are where you seem to be expecting to see the cache, several kms northeast. You also mentioned that only the 1st stage should have its coordinates published, but in the Additional Waypoints section of your cache page, the coordinates are also provided for stage 3.

You mean this one? Again, this is at a different location than your map link in your first post. Where did you get that link from? It's pointing to a location several kilometers to the northeast of both your caches, so it's not surprising that you can't see the cache.

Are you looking for it on the map by its posted coordinates, or the final coordinates? It will always show on the map at the posted coordinates, whether it's your cache or not. Even if you use the new "Corrected coordinates" feature, Groundspeak hasn't yet completed the functionality to show the cache in its corrected position on the map. When I bring up the map from the above URL, it centers the map in a different spot several kilometers from the posted coordinates. On my screen resolution (1680x1050), your cache was just barely off the bottom left corner of the map. If you go to the cache page and click on the "View larger map" link, it will bring up the Beta map centered on your cache:

I can confirm I was seeing exactly the same thing last night. It had been working fine since the last update, but last night it displayed the described symptoms: map missing, large chunk of code at the bottom of the page. Refreshing and restarting the browser didn't work. I didn't try it earlier today, but when I tried it just now, it was working.

Hmm. I just tried viewing jellis' stats, and then my own, and it worked fine. It definitely wasn't an isolated instance, because at least 2 of us experienced it, but it does appear that it was either temporary or intermittent. I'll keep an eye on it.

Why is this "DECLINED"? I'm seeing exactly the same thing. It does eventually come up, but LONG after the rest of the page has loaded. There is most definitely a bug here. I'm seeing it on FF8.