Travelling-MnM

Thanks hleeful. That fixed the problem. I got my points.

Gill & Tony, as far as I can tell the log date is based on the time zone of your computer. I leave my laptop on GMT but my phone picks up local time. This can lead to odd results if I use them alternately to log caches. Presumably if they used log dates you could fake the data just by setting the clock on your PC. (That might still be more user friendly than the current scheme.)

Thanks Keystone. You are almost certainly right. I am probably remembering a comment made about reviewer accounts as if it were about cache placement.

Unfortunately I can not find it now. I think it was in the guidelines for cache placement when I read them about 3 years ago. The purpose, as I remember, was to separate correspondence for cache placement from other correspondence. I have checked a couple of reviewers who have published local caches (Long Man & Castagnari) and they have 38 & 44 finds respectively. I imagine that most of their geocaching is done using other IDs.

What happened today? We saw that our score had reset to zero as planned at 05:00 PDT. We then logged a new find (GC5RQF6) at about 06:00 PDT (14:00 BST) but our score did not change. We were getting a lot of server error messages at about that time. Did that cause caches to be excluded from the Friends League scoring or is my time zone conversion wrong?

We logged a cache at 06:00 PDT (14:00 BST) but it was not counted, even though the reset from the previous week had occurred (our score was back to zero before we logged the new cache. The system was very slow - even giving HTML error messages like 'Server not responding' - at the time. Has this challenge overloaded Groundspeak's servers and caused caches to go unscored?

I guess the question is what is your local time when you are travelling - the time at your home or the time wherever you are (which can go backwards when you change time zones!)

I seem to remember that there is a recommendation on geocaching.com that caches should be placed using a different ID from the cacher's normal one. I have certainly heard this from a reviewer. Obviously if you do this you are hiding caches when your ID shows zero caches found.