New member is suspicious!! Possible Bot?

[KX6D]

This new basic member, CaddCache, has been quite busy posting DNF's every minute. It's been showing up on the old original caches I watch and could be a bot. Someone should look into it!

 

 

[+Max and 99]

Maybe. But the logs do say he's relogging from a different profile. 

[+cerberus1]

20 hours ago, Max and 99 said:

Maybe. But the logs do say he's relogging from a different profile. 

 

Yep.  'Relogging' long-archived caches too.  How would a two-day newb even know where to look?

We know dozens of 'kids-now-grown' that are reentering the hobby, and now logging caches found with mom n dad.

In fact, we gave away geocoins to many, and they now have accurate track of what caches the kid was with them by 'dipping' it (now called a Visit log) to each cache present.   

[+JL_HSTRE]

On 4/29/2025 at 7:18 PM, Max and 99 said:

But the logs do say he's relogging from a different profile. 

 

Not good to relog DNFs when doing that.

[+Max and 99]

Just now, JL_HSTRE said:

 

Not good to relog DNFs when doing that.

I agree. 

[+fuzziebear3]

4 hours ago, Max and 99 said:

I agree. 

Why not?   As long as they are post dated with the actual date of DNF, it will be buried and not matter to the cache.

 

 

[+Max and 99]

13 minutes ago, fuzziebear3 said:

Why not?   As long as they are post dated with the actual date of DNF, it will be buried and not matter to the cache.

 

 

Yes. 

[+JL_HSTRE]

5 hours ago, fuzziebear3 said:

As long as they are post dated with the actual date of DNF, it will be buried and not matter to the cache.

 

Many re-logs with a new account aren't backdated.

 

Even if correctly dated, it incorrectly adds another DNF. A cache with 100 Finds and 5 DNFs it probably doesn't affect much if properly but a cache with 10 finds it might.

 

The CO and anyone watching the cache may not notice the old date and mistakenly think it is a recent DNF requiring action. 

[+niraD]

11 hours ago, JL_HSTRE said:

The CO and anyone watching the cache may not notice the old date and mistakenly think it is a recent DNF requiring action. 

That's why backdated logs of any kind should include an explanation of why the log is backdated (e.g., catching up on field notes drafts, team member creating individual account).

[+paleolith]

On 5/1/2025 at 1:55 PM, fuzziebear3 said:

As long as they are post dated with the actual date of DNF, it will be buried and not matter to the cache.

 

But these were not backdated, at least not the one I got notice of. It was dated 4/29/2025. I sent email to the New Member explaining that they could and should log the original date and why it matters. I got no reply and the log date has not been changed.

 

On top of that, New Member almost certainly did not DNF the cache at any time. It's GC672, hidden in 2001, with 103 finds and not a single other DNF. So I don't know why New Member claims to be "relisting" (what's that?) when if anything they are relogging a find as a DNF.

Edited May 3 by paleolith

[+Viajero Perdido]

Doesn't "the app" (the default app) make it impossible to back-date?

[+Weber_and_Sons]

On 4/30/2025 at 2:11 PM, cerberus1 said:

Yep.  'Relogging' long-archived caches too.  How would a two-day newb even know where to look?

We know dozens of 'kids-now-grown' that are reentering the hobby, and now logging caches found with mom n dad.

In fact, we gave away geocoins to many, and they now have accurate track of what caches the kid was with them by 'dipping' it (now called a Visit log) to each cache present.   

I have only been geocaching for a year but I know how to do LOADS on geocaching.

[+brekkcaching123]

I created a new account 3 years ago which is this one. I backlogged all of the caches I found but I didn't change the date, a few COs asked me for Clarification on the finds and I just told them that I was backlogging and they were fine with it. If they logged any of your caches, maybe message them?