Sandy

We really appreciate this type of feedback, so thank you to all who have contributed to this thread. Please keep the feedback coming! We will be checking back intermittently, and especially in the new year.

Working backwards, this is the last day to submit NYE cache hunts. That would be a cool way to bring in the New Year. We are very interested in this project, so get those caches submitted on time!! not getting this, could be very well related to the 12 hour days i've been doing for the past two weeks, why today and not on the 17th? Sorry, "this" = 17th. I was just reiterating CacheDrone's point that this coming Saturday is the cut-off point.

Geocaching: Review Process: Hiding a Geocache: Challenge Caches updated.

Well done Groundspeak! Partnering to provide service to an obsolete OS. Windows Mobile is SO out of date they changed the name Windows Phone 7 and 7.5 is current should you be interested in breaking "the one step forward, two steps backwards" cycle! As Moun10Bike points out, the API is open so that developers can build an app for whatever platform they want. The work being done by external developers in no way affects what is being done in-house. This comment is ill-informed and disrespectful. Please post with more care.

Working backwards, this is the last day to submit NYE cache hunts. That would be a cool way to bring in the New Year. We are very interested in this project, so get those caches submitted on time!!

Done! We will continue to use this thread to update our users to additions of edits to the Knowledge Books. In addition we will add a manual time-stamp to each edited or added page. This practice will start now, and will affect subsequently updated or added pages. We thank you for alerting us to this gap in our communications with you, our caching community members. Cheers!

Groundspeak has discussed this aspect of EarthCaching and included the GSA in the discussion. We will leave EarthCaching as is for now, with the ability to create PMO EarthCaches. Thank you for raising the discussion point.

Oh, well, that's a great idea. Simple and elegant. Thanks, Keystone. Agreed - do not despair yet.

Yup. Like it. We are discussing all options. There is a large group that contribute so we need consensus. Will keep you posted.

Please note that the Knowledge Books are still a part of our user support, but that the page is renamed "Help Center". For more information, see here.

Hello everyone! We have changed the name of this page to "Help Center". We now link to that page from the site footer and the top navigation "Play" menu. We renamed it because we hope that more cachers will find the help that they are looking for with a more intuitive name than 'Knowledge Books". You will see that the Help Center still contains the Knowledge Books, but we also highlight the 'email us' function and other places on the site where users may find the information that they are looking for. And as always, if you have feedback or questions, you can email contact@Groundspeak.com for individual support.

Some good points here. Help Center is more apt because it contains the Knowledge Books and access to an email portal. There will be an update to that page going out very shortly. To your point about the updated KB pages, we understand that having a list of updated or added articles would be helpful to users who are subscribed to that thread. Maintaining this thread, however, has become far more involved, as there are now a team of lackeys that contribute to the various sections of the KB. Point taken, however, and we can discuss whether or not to continue updating this thread or another like it. We do not have a way of reporting on previous version of the KB articles. Thanks!

Suggesting that this thread loops back around to caching. Dogs + caching is fine. Dogs + training + errant owners is, well, for a pet site.

This product is a non-Groundspeak product, with a webpage that contains banner ads for other companies. Closing this thread.

Groundspeak wants to hear from our users about how to better your experiences on Geocaching.com. Comments such as these, however, are outside of the realm of constructive criticism. It wasn't personal, it wasn't rude, it WAS factual. Editorialising is not fact reporting. We aim to listen more closely and to serve this community as best as we can, but the comment posted by Moun10Bike is to reiterate that we cannot do everything that is requested. Excuse me? Top 5 requests from the Feedback site. Solve a Mystery, Under Review. Phase one is implemented, and Phase 2 is coming. Nano cache size, Planned. We've been asking for EIGHT YEARS.... Is coming in the early new year with the other GPX enhancements. Further, this was a philosophical decision. Nanos were not as prevalent in the game eight years ago, so claiming that this has been pressing for all that time is not accurate. Support Wherigo, Planned. Last update was in 2010 for the unsupported WinMo. It is planned, but this is not a quick implementation - and don't be cheeky about that statement. New cacher Guidelines, Under Review. We are still reviewing this and working on the best way to implement. You will see more on this in January. 3rd Party API, still waiting. It is highly unlikely that the 3rd party API as you describe it will be implemented. We are not an open source project. Please be respectful in these threads. Making empty promises isn't respectful. Agreed. And we are doing much better at not promising what we cannot deliver. This is exactly why some things will be declined. You, however, are not being respectful.

Judging from all the many little bug reports that I've noticed concerning things like how emails generated from logs submitted through the API are different from emails generated from logs submitted on the website, I'd say that Groundspeak isn't a big fan of code re-use Just a reminder to be respectful in these threads.

How true... Groundspeak wants to hear from our users about how to better your experiences on Geocaching.com. Comments such as these, however, are outside of the realm of constructive criticism. We aim to listen more closely and to serve this community as best as we can, but the comment posted by Moun10Bike is to reiterate that we cannot do everything that is requested. Please be respectful in these threads.

But why did you restrict the Groundspeak website forum area to premium members only as writing access is regarded? Are only PMs eligible to identify bugs and report them? Cezanne being fixed as we speak - thank you for bringing this up.

We will have our official messaging presented at the next site release (currently scheduled for next Tuesday, Nov. 8). I suspect you already have it all hammered out, and it may be too late for suggestions, but the idea of heading the subjects with [bUG] or [REQUEST]... wouldn't it be more efficient to simply split it into bug and request forums? I think it would be much easier for us to look through, at least, and I suspect the same would hold true on your end. Just a thought. 4 sections is easier to maintain than 8, so this will work well for us and the team of forum Mods who will work with us.

Whatever that means. It means that there will be more clarity, better community support and more eyes on user reports and requests. Yes. At the time I wrote that, we knew very little. I wasn't trying to be a smarty-pants.

Whatever that means. It means that there will be more clarity, better community support and more eyes on user reports and requests.

So now we'll have the old-school bulletin board style forum and the new-fangled bloggy feedback website. Both for suggesting changes to the system. Not the best idea GS has come up with methinks. We are not finished yet. At the next site update all changes will be implemented.

It means: "Nice idea, but we can't be bothered actually implementing it. Instead, we'll just tie up your votes indefinitely so you can't annoy us with any other ideas" No, it doesn't. That said, we are working on more effective ways to communicate what we do mean when something has been reported to engineering.

We agree that this part of the cache submission process is not intuitive and are determining the best way to address this. We appreciate this feedback, and it is particularly great to see community members helping out a fellow cacher in this thread.