lex3001

I've noticed in my limited experience that some caches seem to be more prone to trackables going missing that other caches. Personally I try to help a trackable along its goal and I would be willing to take into account how likely the next cache I place it in is to be a good home. I believe there is sufficient data to provide some insight into what percentage of trackables go missing once they arrive in any given cache. The statistics could be updated to include the recent trend vs the entire history as well as updating when a trackable that was thought to be missing is in fact later recovered somewhere else. Sure, the statistics wouldn't be perfect, but they may provide some insight in behavior around a certain cache. Another idea would be use to data analysis (who viewed what caches) to try and determine what geocaching users might be keeping trackables that they shouldn't be. This would be no exact science, and since it would not be prove-able, I'm not sure what you would do with the results. SO maybe we'll table that one for now... If you are looking for volunteer programmers to work on this kind of thing please email me, it would certainly be an interesting project. What about making all the data open, or at least what might be considered public data? -lex3001

I am also getting archived caches in search results now. For example, searching in 94709 brings back King Cahce which is archived.

Is it possible that this site update is what broke the Windows Phone 7 app for everyone? At least 20 users have reported problems and it seems that the problems may have started at the same time as the site update. At first I thought it was the new version of the WP7 app, but now I think it is actually the site update... Please look into it, I had some caching planned this weekend and rely on the WP7 app! ;-)

Interesting -- I cannot recall exactly when I installed the new version, but this problem just started. I clicked on Help in the app and there was a link to another forum or something where about 20 people have reported this same issue. I've got the LG Optimus / 900. I DID notice last weekend that out of 4 logs I entered and sent from the phone, only two actually got posted to geocaching (but no errors)... I wonder if that is related somehow. After reinstalling the app today (and noticing that is now only $9.99, I paid $19.99!) I had to try and log in about 20 times before it finally worked... but still not cache search results. Fortunately my wife does have the app on her iPhone still ;-)

Here is an update: I uninstalled the app and reinstalled it, and now I get that error doing almost anything such as logging in etc. Is it possible you have set a global network timeout to 1 or 2 seconds? Anyway I am also a WP7 phone developer so let me know if you need any help debugging... but this new version is unusable! Thanks

I have been using the WP7 phone app for a while and I recently got an automatic update from the marketplace (I think it must be this release you are referring to). Since then, whenever I try and get a list of geocaches near my current location or near a specific address it says "Network error: Unable to contact server. Please try again later. OK". Everything else works fine, including looking up my badges, etc., and no problems with the network or other apps accessing the Internet. Even in the geocaching app I can clearly see my location update in the Bing Map. Also, geocaching works fine on my wife's iPhone still. This seems to be a problem specific to the latest version of the WP7 app.

I have a cache which is a hollowed out bolt. After several months in the rainy season I have noticed that the cache is getting rusty on the inside. Any advice on how to best keep this cache going as long as possible? I was thikning of oiling it and then drying it (mostly) out again. Or maybe WD-40?