Return to Project-GC

Welcome to Project-GC Q&A. Ask questions and get answers from other Project-GC users.

If you get a good answer, click the checkbox on the left to select it as the best answer.

Upvote answers or questions that have helped you.

If you don't get clear answers, edit your question to make it clearer.

Is a cache visible before it is actually published?

+2 votes
63 views
I have placed a new cache and it was published today.

I set it to premium member only and so i am able to see the audit log.

The cache was published on 03.09.2018, at 08:01.

In the audit log i expected only to see the reviewer and myself.

But in the log are 50+ cachers who visited my cache since 02.09.2018, 23:01. They are all regional cachers.

Is there a way to see the cache before it was published? Or is there a way to get the GC Codes, that will be published within the next hours?

Thx
asked Sep 3, 2018 in Miscellaneous by NoobNader (Expert) (15,940 points)

1 Answer

+2 votes
 
Best answer
No, the cache is not visible before publication to anyone but you and a reviewer.

I suppose, the 8:01 and 23:01 is the same time just a different timezone (one of them in US, second in your timezone), because once the cache is published, many people just open the page or download the cache to figure out what is going on.

Please, clarify in what timezone you are, how the what was the timestamp you received the publication mail and how the times in audit look like (including potential time zone identification).
answered Sep 3, 2018 by Jakuje (Moderator) (89,410 points)
selected Sep 3, 2018 by NoobNader (Expert)
I see, the publish mail had the timestamp 23:01 in it. So I understand, that some of the visits where recorded with that timestamp, too.
I am sitting in the MESZ (European Summer Time, Hamburg, Berlin...) and the timestamp was Seattle time..

Just wondering why the cachers from my timezone have the timestamp from Seattle..

Thank you a lot. It helped me understand this.
Its not that they would have that timezone. The timestamps are recorded only on the geocaching servers so this is probably just oversight/laziness/bug in the rarely used function of audit from the side of Groundspeak.
...