Sandy

The 'change' was a decision, so does not need to be corrected. This is not a financial decision, but a decision to divide the UK and Ireland regionally. This has been explained in this thread, as well as in our public article, and is not something we are hiding from. Although there have been some complaints in the past year, and we can see that side of the argument, we are going to maintain the current usage.

I do understand, yes, but I am being honest when I say that we have no intention of making a change to our 'incorrect' use of the term UK. It is not a matter of assigning fault, but a conscience decision. That you disagree is noted, but we will not be changing this use of the term UK.

Groundspeak understands that this is an often-discussed and contentious matter. The article previously linked to explains that the regions have been denoted geographically. We will not be making a change, as this has been carefully considered, both by Groundspeak and the local volunteer team.

HTML on cache pages German version (6.5) updated.

I'll try to remember that when I have a meeting with Groundspeak later this week. I don't know if you're just supposed to contact the developer, spstanley, directly or what. (On a side note, it appears he's on a one-a-day streak since May.) I cringe when I think of submitting bugs to Groundspeak because there have been times I've done so and later had to badger them repeatedly before they were addressed. Groundspeak acknowledges that there have been times when bugs have not been addressed in a timely manner. We are working on our best practices and specifically to address this exact problem.

Please email it to contact@Groundspeak.com and mark it Attn: Moun10Bike so we can get it straight to him. Many thanks!

Additional users affected by this bug are asked to write to contact@Groundspeak.com so we can track your cases. Please understand that Groundspeak's hands are tied on this bug, We have not been able to reproduce the perfect storm of factors of this bug. When we ask you to troubleshoot, we are not asking you to do our job for us, but only to help us pinpoint the exact situation that causes the bug. We are as frustrated as you by the persistence of this bug. We continue to assess the additional information that us provided.

It is not possible for Groundspeak to respond to every request that is posted in our forums. We are, however, watching the forums and for those features that have user support, and are viable. That is the promise that we can make to our users. We will continue to respond to all bugs reported.

This question has been addressed here. Closing this thread. The opening poster is asked to only post one thread about the same topic.

Hi all, What we hope you realize is that we aim to reply to these reports or feature discussions in a timely and informative manner. There is no playing of games. Not only do we not want to do that, we simply do not have the time to dedicate to messing you about. The team that works to troubleshoot issues, discuss and consider feature requests and report these matters to the engineering team, has a variable workload. At times we are able to step into the forums more actively, because the many other aspects of our work are taxing our time less. But there will be times when the response our users get is succinct, because we are working on more of the back-end stuff. At no time are we sitting around plotting ways to mess our users around. And when those sorts of comments are posted in our forums, our time is then spent addressing behavior that violates forum guidelines. This is frustrating, as we would rather spend our time working on bettering the site for you. And as always we greatly appreciate the time and effortsof those who take the time to post requests and report bugs. Thank you.

Thank you to all the cachers who responded to this cacher's question. I have had to edit out the link to the spoiler video, as a precaution. Some videos posted external to our site container spoilers about a cache without that cache owner's permission.

Groundspeak and the GSA have discussed this question. Please keep an eye on the FAQs on EarthCache.org in the coming days, and you will see the updated position. Cheers, everyone.

Thank you. I'd just like to mention that the formulation cited by the OP is not part of the guidelines, it is just part of the faq. These are two separate documents and EC hiders only confirm to have followed and read the EC guidelines. Moreover, the formulation discouraged appears to mean that it is possible to come up with EC that are not 24/7 accessible under appropriate circumstances. Otherwise, they would say it is forbidden or not possible. Cezanne Understood - we are discussing whether the guidelines should be updated, and/or how better to clarify best practices for EC owners.

Groundspeak is talking with the GSA about this aspect of the guidelines. We will let our fellow EarthCachers know of any update.

This issue has been pinpointed and fixed. Thanks for the report!

Can you please forward the GC code to Groundspeak - or post here? It may be that there are details associated with this cache that meant it was published after special consideration.

Updated: Geocaching 2.4 Newest Caches to Me

This forum is intended for users to discuss features related to the Geocaching.com web site and Groundspeak's mobile applications. IMPORTANT: For general questions about the website or apps, or how to use the website or apps, please email contact@geocaching.com or post here: How Do I...? To report a bug, please post here: Bug Reports Please help us by following these conventions when posting a new topic: Search through the topics here to see if the feature or idea has already been posted Separate individual feature discussions into separate threads for ease of tracking and discussion Clearly summarize the details of the feature in your initial post We will watch for and read newly-created threads, but we will not be able to respond to all threads. Suggested features are discussed and prioritized internally, and we consider community support in this process. We cannot guarantee that submitted requests will always be implemented.

Forums.Groundspeak.com will be going offline temporarily for a site update on Tuesday, December 27, 2011 at approximately 5pm PDT (convert to your local time here). The update to the forum server should take less than one hour.

New article: HTML in Cache Pages auf Deutsch

My previous post in this thread was to send our condolences to the family and friends of this cacher. At 21 he already contributed much to the game. We are deeply saddened at Groundspeak. Since this incident, Groundspeak has received some requests to archive caches that are deemed by the community member as dangerous. We do not want to archive listings based solely on a complaint of this nature. However, if a cache is reported to us and that cache meets the placement guidelines, we will contact the Cache Owner to let them know there has been a complaint. They may opt to update the cache page with some cautionary text. When a cache is reported that does not meet the guidelines, we will take action. As the location is not checked before the listing is published, we rely on the community to speak up when a cache is placed inappropriately. That said, it is important to discern between an inappropriate placement and one that is particularly difficult and could put a cacher in a dangerous situation. A caches rated 5/5 may require a cacher to abseil off a cliff, which many would consider to be dangerous, but we will not be restricting cachers from placing caches of this nature if they meet current guidelines. If you know of a cache that is inappropriately placed, and you do not want to post a Needs Archived log on the cache page, you can email Groundspeak so that we can look into the matter. Again, our deepest sympathies for the loss of this cacher.

Regardless of the disclaimer on the site, Groundspeak is always sad to hear of the death of a cacher – particularly in the pursuit of the game. We are part of one big community, and this type of death always has an impact. Our thoughts go out to the family and friends of this cacher. As always, we hope that cachers will take care while geocaching.

This update was a pre-emptive fix to ensure that the server issue we encountered at 4am Seattle time last week, would not recur. We thought that taking the site down for an announced 15 minutes would be a far better option than having it crash for an undetermined amount of time at a later date. As always we apologize that there was any inconvenience caused.

Surely, it should be SUBMITTED then. Just to reiterate Moun10Bike's comment, we do not submit a bug into our system until we have reproduction steps. That is the role of the lackeys who have initial contact with our users. Most of the time, the bug is reproducable but when it isn't we turn to you to help us determine the perfect storm of factors that are creating the bug. Sometimes these bugs only occur within the scope of a specific set of circumstances. We truly appreciate those that help us to pin it down.

Closing this thread. Please do not use the forums for solicitation - and especially of 'questionable' official merchandise.