ScurvyPlunderers

Well, after no answer or action taken by Groundspeak HQ from Saturday through today, I just deleted the ones on our caches. So much for a help request. There couldn't have been a more blatant example of fraudulent logs for them to work with. I need to correct the above. There was an un-noticed response to my HQ email that showed in a string format... They did respond to me by name and thanked me for bringing the matter to their attention and that it would be dealt with appropriately. I do thank Groundspeak HQ for this.

So...my email/message was about his reasoning for these multiple same day entries and why I find no physical log entries. His answer; "Hello". My reply was a little shorter asking again why we find no log sign-in's. His reply; "I’m teaching at my friends account then I will remove cache log sheet". I then contacted HQ, outlined the situation, and asked how these fraudulent entries can be stopped. I told them 466 entries is an awful lot of teaching. You don't "teach" live on-line, like all of us you read the rules and go out and play. All not funny, but maybe a story you can tell other users about. I've never read about something done to this extent before.

Will do on the post if I hear back or not. You all looked deeper than me, but I noticed in scrolling his logs this am that a whole page is on one CO. So a lot of CO's are getting multiple emails today. Be interesting to see if the 406 starts going down, down, down.

Thanks for the quick responses. The caches we know of around here are all scattered, some on trails so nothing grouped. We just emailed and messaged...we'll see. Good one on the food.

Hi, over the years i've read some on this discussion but have a question... We just received a number of same day logs on some of our different caches. Turns out this user has posted to 406 caches today, from here (in California) to Turkey. Can the reason be, maybe, that he’s split from a duel user name and he wants to post old finds under the new name? No physical logs, we don't want to delete finds if there is a reason for this.