Xaa

Wouldn't it be nice to have a Netherlands forum here as well? Belgium has one, even though there is a geocaching.be. I don't see why the same thing couldn't go for the Netherlands.

There are more issues than just the dropping TB's in unpublished caches. Some of which seem so incredibly easy to fix that you wonder why they are not fixed. Then again, it's only FTF, who carez...

I suppose these are nice stories, I guess cache owners will laugh when they read the logs, as long as it is done respectfully and legally. I'd say there is a big difference between your examples (someone trying to make this a challenge trying to outsmart the owner in a perhaps funny but relatively respectful way), or people who just trade end coordinates so they can put their name on a piece of paper.

Doesn't this make victims amongst people who are doing your cache in the decent way? What happens regularly with me, is that I get stuck somewhere (either a WP is missing, I misread stuff, can't find it, all kinds of everything can happen that can make life difficult), find a bench, look really good at what I might have done wrong, and how I can try to find back the right track, possibly missing a WP but at least finishing the cache as it was intented. I suppose this is handled in good manner? If so, this might be a decent solution. The only thing it doesn't stop (of course, since nothing stops that behaviour) is people who take a trip and log for a few friends as well. (Which is happening here in my country, or at least I have serious suspicions that it is happening)

Do you get notifications of every time a pocket query with your member-only cache is sent? Sounds unlikely, so it doesn't really give you any extra "security"

As far as I'm concerned that would be the best improvement they could make, yes.

I guess this question pops up something like 4 times a week :-) So the answers shouldn't be too hard to find. Go to 'my account', on the right you'' find Set up notifications

Maybe it was just a temporary glitch? Everything seems to work fine on the cache page you mentioned

Yes, like he said, it's getting a notification emailed to you when a cache is published.

In my country there are at least a handful of mysteries where you have to download executables even. Obviously there are a lot of people who don't mind doing that, and the reviewers don't care as well (they were approved with those guidelines in place, and some of those caches were even pointed out afterwards). I wonder if people would change that attitude when the first person comes around abusing it (hopefully in a whitehat way, just proving a point). Then again: if you get your cache approved and add a link afterwards to some malware, the reviewer is easily bypassed, so the guidelines don't really help here.

What's the fun in showing something statically that might be right some of the time, if you can do it dynamically wrong most of the time?

I've noticed a difference between dates in pocket queries and on the website. The pocket queries have log dates, including a time in hours/minutes, which perhaps is in GMT where the website is using them in Groundspeak's timezone. The result is that some logs (an example is the log on 2008-04-29/28 for cache GC13GFR. This log is on the website as April 28. In the Pocket Query you'll find <Groundspeak:date>2008-04-29T04:29:28</Groundspeak:date> Is this a bug or a design choice? And if it is a bug, could it please be fixed?