DanPan

Reasons for PMO Caches Groundspeak does not state a reason for PMO caches. However, cache owners have stated various reasons for restricting their cache listings to premium members, including: Hiding cache coordinates from local cache maggots who have only basic accounts. Encouraging others to buy premium memberships, or rewarding them for doing so. Keeping the cache listing out of products that include preloaded cache data (that don't require a geocaching.com account). Preventing search engines and unregistered visitors from accessing logs and photos posted to the cache. Rewarding premium members with an FTF opportunity (switching off the PMO flag later). Reducing the traffic to the cache, to reduce the maintenance required (e.g., replacing full logs, resetting on-site puzzles) or to reduce geotrails. Slowing down the initial rush of traffic to the cache site, to attract less attention from muggles or to reduce geotrails (switching off the PMO flag later). Limiting access to "serious" geocachers, expecting them:to treat the cache/camouflage/location/contents with more respect. to know how to log trackables correctly. to post better online logs. to have validated their email addresses. [*]Hiding a mystery/puzzle cache that requires premium membership to complete, so basic members don't see it.[*]Hiding a challenge cache from basic members who might not understand the need to complete the challenge before logging online.[*]Hiding an EarthCache from basic members who might not understand the need to complete the EarthCache requirements before logging online.[*]Hiding caches from local basic members who complain excessively (e.g., about caches that are "too difficult" or that cost money to find). post bogus Needs Maintenance or Needs Archived logs (e.g., whenever they DNF a cache). [*]Using the audit log feature of PMO caches.[*]Being curious about what it's like to own a PMO cache.[*]Wanting to take advantage of all the features offered to premium members.

With some magic algorithms you will find upcoming caches in favorite points and caches that are popular right now. shortcut to Map & List "What's hot?" in UK

List with all caches that have "CPoS" in the name.

Zoals Jurgen & co reeds aangaf, wordt het probleem wss veroorzaakt door "&" in je loginnaam. De meeste forums ondersteunen geen speciale karakters (&, @, #, ...) in loginnamen.

It is corrected now. Thanks Cardinal Red for the quick fix!!

This cache GC20Q89 was last found on 08/aug/2013. In the "search for geocaches" the last found date is 24/sep/2012...

API is doing fine right now.

If you look at you will see that today the avg response is twice as normal. Geocaching.com resonse time: Sep14 546ms Sep15 660ms Sep16 555ms Sep17 564ms Sep18 548ms Sep19 523ms Sep20 937ms (2x average performance per day) Geocaching apps response time () Sep14 874ms Sep15 869ms Sep16 879ms Sep17 881ms Sep18 899ms Sep19 841ms Sep20 1264ms (50% increase)

"Refresh cache data" and "Download PQs" in GSAK: errors and slow/no response... Please have a look. Generating GPX file ... no response after 20 seconds 20/09/2013 21:34:14 api call was successful ... no response after 20 seconds 20/09/2013 21:43:50 api call was successful ... no response after 20 seconds 20/09/2013 21:53:09 api call was successful ... no response after 20 seconds 20/09/2013 22:00:58 api call was successful ... no response after 60 seconds Previous request ended in error, now doing a retry.... 1/10 Retry delay started: 120/120 20/09/2013 22:16:24 api call was successful ... no response after 120 seconds 20/09/2013 22:24:18 api call was successful ... no response after 180 seconds Previous request ended in error, now doing a retry.... 1/10 Retry delay started: 120/120 ... no response after 120 seconds Previous request ended in error, now doing a retry.... 2/10 Retry delay started: 120/120 Previous request ended in error, now doing a retry.... 3/10 Retry delay started: 120/120 ... no response after 20 seconds Previous request ended in error, now doing a retry.... 4/10 Retry delay started: 120/120 ... no response after 180 seconds Previous request ended in error, now doing a retry.... 5/10 Retry delay started: 120/120 ... no response after 120 seconds Previous request ended in error, now doing a retry.... 6/10 Retry delay started: 120/120 ... no response after 20 seconds Previous request ended in error, now doing a retry.... 7/10 Retry delay started: 120/120 Previous request ended in error, now doing a retry.... 8/10 Retry delay started: 120/120 ... no response after 120 seconds Previous request ended in error, now doing a retry.... 9/10 Retry delay started: 120/120 ... no response after 60 seconds Fetching Pocket Query: Foundinthelast7days PercentDone: 20 ... no response after 120 seconds ... no response after 60 seconds ... no response after 20 seconds PercentDone: 100 Fetching Pocket Query: allcachespart15 PercentDone: 20 ... no response after 120 seconds ... no response after 120 seconds ... no response after 20 seconds . no response after 20 seconds PercentDone: 100 Previous request ended in error, now doing a retry.... 1/10 Retry delay started: 120/120

Since a few hours, Geocaching.com site is extremely slow and the API does not respond anymore. I'm on WEB10.

Een alternatief: Top Favorite Caches NL Top Favorite Caches NL (%) Top Favorite Caches NL (Wilson score) Je kan ook nog extra filters toevoegen zoals b.v. cache-type, cache-grootte, provincie of gemeente, difficulty, terrein.

The Bookmark List Korte multi's in Noord-Brabant by *BaJo* is not public anymore.

Find Bad Logs

We found the root cause. Our hosting provider did an upgrade of PHP to a newer version, which is incompatible with the current version of the forum software. I keep you informed.

oliantoine, Merci pour le message. Nous étudions le problème dès maintenant.

It seems to be fixed. Thx.

It seems to be fixed. Thx!

In meantime you can http://jeep.geocaching.com/seek/nearest.aspx

If you click on the Favorites ribbon to sort the caches by favorite points, it returns with "Search For Geocaches".

Today, loading images from the gallery and avatars on cachepage is very slow. Please have a look.

Indeed, the scrambled images are back again. Very annoying to see my avatar popping up in someone else gallery...

Met volgende tool kan je snel je dubbele logs opsporen: Find Bad logs Dubbele logs verwijderen zal nog steeds één voor één moeten gebeuren.

Fixed in Release of August 21, 2013. Thx GS

Fixed in Release of August 21, 2013. Thx GS