supertbone

I love LPCs. Please keep them coming!

I've seen some challenges that skirt the rules. There are a couple in the Los Angeles area that require the user to log a range of caches or waymarks.

That is the eternal question isn't it?!

Legal? I seriously doubt a governmental entity has limits on how much someone can find in a day.

I save mine for virtuals and earthcaches.

I have just tested the Facebook integration and it works, though I wish the facebook post would show the name & GC code of the cache I found. Twitter on the other hand still does not work when logging from the Android app. I tested this with on one of my caches (GC2MF0W) using the authorization I currently had, then I revoked it and redid it. Both had the same results, no posts to my twitter account. This last worked for me back in May.

I've seen QR codes used as stages.

_

People get worked up of minor things. Who cares what they are called?

I usually sign after the last signature, unless the log is a nano and then I'll sign at the first black spot I come too or a full log where I might write in a corner or the side.

I know of another that exists on National Park land. GC1YFAN

Either way, I still wouldn't care. You seem to care enough to tell us, at least twice, how much you don't care. I do care though. I think there are good reasons for the proximity rule, and if it's nullified by people gaming the system, I see that as something harmful to geocaching. Well said. To answer the OP: this exact same situation temporarily migrated to North San Diego County for a few years. I spent some time working in SLC; coming home to cache the same geo-trash was frustration writ large. I always wanted a PQ filter to ignore all hides by that UID. By definition, 2500 caches are all trash. If you can't or won't maintain them, they're trash. There are hundreds of cachers who want to create that something special cache but simply cannot because of a rolling mass of crap that archives itself and is reborn periodically as more crap. Finding and correcting one out of the lot after a whack of forum posts is not a confidence builder in the reviewer community or process but a confirmation that they only have time to address issues when they are specifically raised. Shame won't work in this specific case but I think it's the right tool most of the time. The caches are only meant to be found by a small number of cachers in any event, not the community at large, so appealing to the greater good and all that jazz is not likely to work. Boy, you are a fount of positivity this morning. Who are you call all of someone's caches trash, especially when you have only a small hand full of his caches?

I love micros!

That's the trick!

Its always great seeing an expert emerge after a year of geocaching. As you state there are areas that are not saturated. If you are so keen on placing a cache, then do it there. Otherwise, first person there, is one to place the cache. And as for your respect of the cacher? its very curious to me on how a veiled forum post, equates your respect of said cacher. He put those caches out there for people like you to find, he is a prolific cacher in your area. Yes some may need maintenace from time to time, and its sometimes hard to maintain caches, because life takes you in a different direction. (Since I haven't cached for a long while, I need to get on a maintenance run soon). So in other words, keep calm, carry on. Nice said!

I'm not trying to split hairs, but cache owners can archive caches. Which is what he did.

My favorite milestone was #2000 when I found The 'G' Spot (GC470) It is high up on a mountainside that I can see from my house. The hike was nice, the views were awesome, and the find was rewarding.

I don't see this. But if they did, how would that effect you?

DrJay has 1638 days straight caching. http://www.geocaching.com/profile/?guid=07c0a989-f408-485d-bc14-57c4c76e28d5

I wouldn't be surprised that the old virtuals get mass archived like the old locationless caches.

They were probably using the FindStatGen Macro in GSAK.

me too, please enable move to SD... I think you can only do that in Android version 2.2 and higher.

The 'send updates to Twitter link' page error was resolved, but the issue of Twitter actually being updated wasn't. It hasn't worked for me since some time last month. I have verified that the permissions are set.

I love the new app! To be honest I have not had an issue with it. It doesn't crash on me like the last one did, plus the feature set is a lot better. Using it on HTC Hero with Android 2.1

Hence the term 'beta'.