TmdAndGG

Maybe quadruple check and make sure there's no space at the beginning. I shouldn't be difficult or frustrating. It's possible it could be a bug.

I don't think a non-geocacher would have poured concrete to protect a geocache. I think the point is that really old caches get extra protection.

Since I'm the official self proclaimed off topic thread announcer, I might as well give the latest report on this thread! It appears to have gone from another challenge cache type request thread, to a tutorial on how to rate the D/T on your caches! Incredible!

That's the point. It's all fun and games until @cerberus1 (or any other random cacher) comes along and finds a cache that was just about to be lonely, that's when the fun ends (Or at least for the lonely cache hunters). And could you please explain how finding a lonely cache helps keep the gameboard fresh? I would say that archiving your lonely cache and putting a new one nearby would be the best way to keep the gameboard "fresh".

No, it is not on the app. The link to it and more information here. https://www.geocaching.com/play/owner?utm_source=geocaching&utm_medium=lihp&utm_campaign=COD

I'm glad it's that way. Oh wait, no one actively participating in this thread has admitted to being part of the "I want to log all physical caches" camp. I guess we automatically win.

If you're talking about the compass screen then there's already a couple of threads on that.

There's only one problem that I have ever encountered with people pre-downloading caches weeks before. You see, there is a park near us that is well known for it's large cache saturation and annual event (Literally ever single spot in the park has been taken. There is no room for another hide without a cache being archived). Every year, within a few months of the annual event, nearly ever single cache is turned over into a new hide. So one cacher, must have downloaded the caches a couple of weeks before heading to the park. When the cacher went, it was right in the middle of the cache-turnover. Two of the caches that the cacher "found" had been archived recently and there were new hides in their spots. The cacher ended up finding the 2 new hides, and then logging them as found on the archived caches in their spots. We promptly messaged the cacher and deleted his logs (they were our caches). The cacher never responded to our message. But they did end up coming back and went to the exact same caches and logging the find on the new caches. Anyways, that's my story.

So what's the point other than that a CO closed his account?

De taal van het hoofdforum is trouwens Engels, als je in het Nederlands wilt posten, raad ik aan om naar het Nederlandstalige subforum te gaan. (Ik gebruik trouwens Google translate, dus de grammatica is misschien niet de beste.) https://forums.geocaching.com/GC/index.php?/forum/122-dutch-speaking-forum-nederlandstalig-forum/ As far as I know, the only way to mass log caches is through GSAK, but I couldn't tell you how (I've never used GSAK). I personally hate C&P logs for masses of caches, but to each his own.

Same thing happened here with a bison tube lid zip tied to a bush. The bottom half of the bison tube had gone missing, but people were still logging finds, even clearly stating that there was only a lid. We logged an NM (or maybe an NA) and it eventually got archived by the local reviewer. There's a local cacher around here who always says, "It's your game, play it how you want"(or something like that). It really is true. If you want to log a find on a lid, go for it. Nothing's gonna stop you. (Unless the CO deletes your log of course)

Only when logging.

Cool! Didn't know that. I guess I have some exploring to do with the new owner dashboard!

If you press the Play button at the top of the Geocaching.com webpage, a list will pop up that includes a link to the new CO dashboard under "Cache Owner Dashboard".

I'm not trying to defend cablevision, I'm trying to defend the fact that it's hard to prove whether or not someone was at the location without a photo or logbook.

Not sure. But if cablevision was location-spoofing, then the same question still poses.

Not exactly. The write note was posted a day after the found log on owlcoconut's first find.

But what if the goal of cablevision's trip was something other that geocaching and the new AdLab was just a bonus?

Okay, fine... I'm just trying to say there's no way to verify that they've been there like a logbook in regular caches, but apparently you guys know for sure whether or not someone has been there...

Because this is how they filter for them:

I agree with the second part, that you can prove that they weren't there if they go find every single AL in a short time, but just because you live on the other side of the planet doesn't mean you can't travel.

I think it's because there's no way to prove that they weren't actually there.

Strange, It works for me...

Or right here!

Read these.