"New Cache" Notifications

[+PlantAKiss]

Hi all. I just had 4 new caches published that I have been working on for quite some time--searching placement space, buying items, creating stuff, doing test placements and corrections as needed, etc. So my cache placement dates are when I first put down my test caches until they were tweaked and ready, some time in May. My caches were published this past Friday. Activity was lighter than I'd expected, especially for the FTFers. I happen to meet a cacher while doing a little check up on a cache and he mentioned that my caches had not shown up on the "new caches" list because the placement date is in May. (As CO, I got NUMEROUS published notifications in my email.)

 

1) Is he right and that is why not many cachers have been out so far (over the weekend)?

2) Or is because it is blazing hot and dripping humid 

3) **IF** the May placement date is causing confusion and slow traffic, can I edit the placement date on the 4 listings since I was actually working on these caches up until a couple of days before being published?

 

I never even thought about the placement date but entered when my test caches were down so I could test coords and correct any issues.

 

Thank you!

[+NanCycle]

I think of placement date as the date the cache was physically placed and distinct from the published date.  But yes, you can edit it.

[+PlantAKiss]

So does the notification about new caches come from the published date or the placement date? If it comes from the published date, then the light traffic might be just cachers are busy and hot. Thanks for the input.

[Moun10Bike]

Notifications trigger off the publication log (i.e. the publication date). However, the "Newest Caches" search on the home page uses the placed date,

[+PlantAKiss]

Thank you! I understand now. 

[+thebruce0]

Yeah it can be confusing when you know there's a cache that's been around for a week, but the Placed date is a year ago because the CO created the listing and perhaps wanted to place a full series, only getting that done a year later. Placed 2022, published 2023. It happens...

[+niraD]

1 hour ago, thebruce0 said:

Yeah it can be confusing when you know there's a cache that's been around for a week, but the Placed date is a year ago because the CO created the listing and perhaps wanted to place a full series, only getting that done a year later. Placed 2022, published 2023. It happens...

Yep. I found a series (with a bonus cache) that was like that. It was originally placed as a private "birthday adventure" for someone the CO knew. Later, the CO reworked it so it could be published. But the date was listed as the original "birthday adventure" date, and the CO mentioned in the listings that FTF had already been claimed, but STF was available.

[+Max and 99]

Oh heck no. I would have logged a FTF on that one even if I was 5th to find it. 

[+thebruce0]

Same, if I claim FTF (proper) on a cache with people who claimed FTF pre-publish, I'd just claim it and clarify FTF-post-publish (as most people consider a "true" ftf)

[+niraD]

20 minutes ago, Max and 99 said:

Oh heck no. I would have logged a FTF on that one even if I was 5th to find it. 

I've also seen caches that suggested (not required, because that would be an ALR) that everyone claim some sort of FTF: First to Find, Fifth to Find, First to Find in a group that includes a toddler, etc., etc., etc.

 

And then there was the liar's cache, which had many elaborate stories of being FTF.

[+thebruce0]

"First to be the 5th to find!"