Weeding out arm chair finds

[Pezcachers]

Is there a way to filter out users who log a cache and have never been to it?
User Trevino4728 logged GC2MK4Q and I know they never have been there or signed the log since I was just there. This user has tried to log one of my caches and has logged a cache I replaced since the CO is no longer active. I call this type of "find" an arm chair find and it changes the points for that cache.
Ken

[Corfman Clan]

This topic has been discussed before. LonelyCache will not get in the business of deciding whether a find is valid or not. Disputed find logs is an issue that needs to be taken up with the cacher, the cache owner, or with Groundspeak directly.

[Pezcachers]

Thanks for the reply.
Pezcachers

[A & J - Adrift]

User Supernaturalteam (a.k.a. Teamspiritsghosts) was created Jan 17th. It's currently blocked.

Over a few days in January they splattered liar logs over a large number of caches mostly in Nevada. Mostly remote mountain ones. They now feature prominently in many places on the lonelycache site.

We deleted their log from our cache GC3XAJF. If any one here has a cache with one of their logs, you should consider deleting it.

[desert dawg]

I emailed Road Runner about this rogue cacher Supernaturalteam about a week ago.

Hard to understand someone would pop for a Premo Membership then log over 240 caches they had not visited .

I have emailed the cache CO's on 3 caches in the Montello area they he bogus logged. all high value LCP point caches. lucky all 3 now have had the liar logs deleted.

Groundspeak has locked his acct, to stop this nonsense, but now how do we get all his bogus find logs deleted? We need to pressure Grounspeak delete all of them?

User Supernaturalteam (a.k.a. Teamspiritsghosts) was created Jan 17th. It's currently blocked.

Over a few days in January they splattered liar logs over a large number of caches mostly in Nevada. Mostly remote mountain ones. They now feature prominently in many places on the lonelycache site.

We deleted their log from our cache GC3XAJF. If any one here has a cache with one of their logs, you should consider deleting it.

[Team Opjim]

There's another one from New Mexico called Kingbee. I've caught him in the act, because several of his logs could quickly be confirmed as bogus.

[Corfman Clan]

Another arm chair cacher, Hippolyte le cousin, has been locked and Groundspeak has deleted all associated logs. Since Groundspeak has deleted the logs, I have updated LonelyCache to exclude that user. This will cause LonelyCache to swiftly delete all associated find logs from its database the next time statistics are updated.

Perhaps someone should encourage Groundspeak to delete all the found logs for Supernaturalteam as well. I'll react to updates Groundspeak makes but feel it inappropriate for me, as LonelyCache administrator, to spearhead this sort of action.

[desert dawg]

Some locked accts Groundspeak has not opted to delete the find logs on. Take Dreamcacher102, they locked the acct back in Aug of 2012 for logging bogus finds, but LCP still has 59 cache finds on that cachers profile, many are high point LCP finds as well. After that long of a time period, I wish LCP would purge those logs clean up and correct the record.
thanks : desert dawg

[chris geertsen]

As I recall supernatural team aka team spirits ghosts was a team account that consisted of a group of people. When one person found a cache, or spirit, the find counted for the whole team, and was logged on that team account. Not one person solely owned that account. The password and username was given out to many people and cachers. When a person or cacher that had the password and username for that account, found a cache, they logged the cache as found on that account. Therefore you see the ridiculous amount of finds. It was considered a group or team account by them because of the many people that used that same account. And as I recall groundspeak does allow for a team or group account, where more than one person can use a given account and or log geocaches they find on that given account.