Jump to content

Has Anyone Else Had Problems With This Cacher?


deetylong

Recommended Posts

I just had the following e-mail exchange with. I don't think I've ever had anyone behave like this before. Have other people had problems with her, or am I really that bad?

 

For those of you who don't know, Geocaching.com archived all locationless caches at the turn of the year. My cache only allowed one finder per mosque. I've been cross-checking the big rush of last minute entries for duplicates, and found that hers was one. Below is the exchange . . .

 

__________

 

-- Copy of email sent to *** *****--

Hello,

 

I'm DeetyLong, owner of the "World Mosques" locationless cache. Thank

you very much for taking the time to log it.

 

Unfortunately, the mosque you entered was already found on October 06,

2005 on by "Steve Brown", so I'm afraid I'll have to delete your entry.

 

Sorry for the inconvenience,

 

-DeetyLong

 

__________

 

--- *********@aol.com wrote:

 

> Oh, Gee, thanks for waiting til they're archived to

> notify me so I can't do

> anything about it.

>

> Thanks!

 

__________

 

Hello! you logged it on Dec. 30! I'm sorry I didn't

stay home on New Year's Eve searching through 400+

entries to see if yours matched.

 

__________

 

--- **********@aol.com wrote:

 

> No, but you could have searched up to 3 different

> days and still found it in

> time for me to find another one. If you didn' t

> want the responsibility of

> checking the many locationless cache logs that came

> in in the last days you

> should have archived it early and taken the 6 months

> free premium membership

> that gc offered and saved EVERYONE the bother.

>

> Thanks for being a bad cache owner.

 

__________

 

Are you crazy? YOU should be the one looking to see if

someone else has found it already! Is one find really

that important to you?

 

__________

 

--- **********@aol.com wrote:

 

> I'm just saying, you could have done this days ago

> and waited till no one

> could do anything about it to make the decision.

>

> I did a word search. I found nothing. I did what I

> could do. I'm sorry it

> wasn't up to your standards. But if your standards

> are so freaking high you

> should be more on the ball about it.

__________

 

If you think requiring no duplicates is "freaking

high" standards, I don't think you're being realistic.

 

__________

 

Whatever. As I said before, I did a search and didn't find one. I guarantee that if whoever someone logged it they didn't identify it properly in their log. I also guarantee that SOMETIME between December 30th and the time that the locationless caches were logged the day before yesterday you had time to look at them, but didn't. My guess is you even saw it but decided to screw people over just for fun. You do that. Have fun. Oops. You did. And you did. Whatever.

Edited by deetylong
Link to comment

Oh man what kind of cheese do you want with your whine! ;) get over it and move on. I never really liked locationless caches, Yes I done a couple but to me it takes the fun out of it.three of the ones I found I logged from inside my car.but to each there own I guess.so thas my rant.

 

But I do think you should not have posted a e-mail just to get people to be on your side in a war over caches you can't log no more.

Link to comment

Geocaching seems to interest many wonderful, generous, kind, and fun people. ;)

 

However, other types of people are also involved in Geocaching. :P Since your communication involved a Locationless cache, that person is probably not in your local Geocaching community and for that you can be very thankful . . . ;)

Link to comment

The cacher attempting this locationless cache has no valid basis for their complaint. A reasonable person knows that they need to search through the locationless found logs to see if the proposed location has already been logged. (Some locationless caches allowed multiple logging of a specific location but that condition was noted on those cache pages)

 

Finding a locationless target is only half the work - logging it requires verifying that it has not been logged by someone else. And... this cacher knew that 12/31 was the published end date. It is unreasonable to expect that a locationless cache owner would be anywhere near a computer during the new year holiday time. Late finds come with a risk.

 

I think most cachers get po'd at some time or other. It is probably best if we write down our complaints with all the raw emotion included and then just don't press the send button.

Link to comment

Cachers should read the page and do the work to be sure that they are not duplicate logging a locationless in my mind. If they do, it is the owner's right to refuse it.

 

With that said, it really isn't worth the worry. I suggest just letting it drop and not worry about it. Don't respond and let it go. Nothing can be done anyway. No reason to dwell on it or get angry.

Link to comment

Personally, I see his point. I owned "Dash for Cache," and I'm STILL sorting through 175+ logs for the last two or three days of the cache. I've deleted several, and will be deleting a few more before I'm through, I'd wager. I try to be fair -- and that means treating everyone the same. If was already found, it's found and can't be repeated.

Link to comment
Cachers should read the page and do the work to be sure that they are not duplicate logging a locationless in my mind. If they do, it is the owner's right to refuse it.

 

With that said, it really isn't worth the worry. I suggest just letting it drop and not worry about it. Don't respond and let it go. Nothing can be done anyway. No reason to dwell on it or get angry.

Yes, well put. If I had been the owner, after taking one look at the "finder's" first e-mail reply, I would have ignored her -- she was obviusly trying to bait the cache owner and start a hissy fight. Some people like that kind of stuff. I do not.

Link to comment

They did a good job not taking responsiblity for following the logging rules and putting the blame on you as an owner.

 

I've had issues like that before and I stick to my guns. Why belittle the work other caches did following your rules by letting someone else skip them? Since the cache is archived it won't be an issue any longer.

 

A handy tip: If you want them to shut the heck up and leave you alone, let them have the last word. It works like a charm most of the time. If they really did want a responce it also puts them in the position of rethinking what they are saying to you since they now want a responce and their last effort didn't work.

Link to comment

One of the built-in features for waymarks is that it alerts you as the waymark category manager and the waymark submitter to a nearby listing. It's just one of many reasons why locationless caches didn't work so well on the geocaching site. Better than that, the next finder can still post a log entry for the item even if they weren't the first to mark it.

Link to comment
If you want them to shut the heck up and leave you alone, let them have the last word.  It works like a  charm most of the time.  If they really did want a responce it also puts them in the position of rethinking what they are saying to you since they now want a responce and their last effort didn't work.

There is a concept full of wisdom and maturity.

Link to comment

deetylong:

 

Your thread was titled "Has Anyone Else Had Problems With This Cacher?" As it happens I do know the cacher to whom you are referring. And in my experience and to my mind she is a top-notch cacher and a wonderful individual who has unselfishly contributed much to geocaching in my area. Although I don't know you I am sure you are also a good cacher who has in turn given of yourself to further the sport/hobby as evident by the time you took in overseeing your locationless.

 

I hope you can put this far behind you and move on. The funny thing is I'd bet you'd get along quite well if you ever happen to meet each other on the caching trail.

 

Bill of B&T

Link to comment

:D Uh . . . Okay. :P

 

Did you read what she said? All that drama for one little smilie? ^_^

--- *********@aol.com wrote:

 

> Oh, Gee, thanks for waiting til they're archived to

> notify me so I can't do 

> anything about it.

> Thanks!

 

--- **********@aol.com wrote:

 

> No, but you could have searched up to 3 different

> days and still found it  in

> time for me to find another one.  If you didn' t

> want the responsibility  of

> checking the many locationless cache logs that came

> in in the last days you 

> should have archived it early and taken the 6 months

> free premium membership 

> that gc offered and saved EVERYONE the bother.

> Thanks for being a bad cache owner.

 

__--- **********@aol.com wrote:

 

> I'm just saying, you could have done this days ago

> and waited till no one 

> could do anything about it to make the decision.

> I did a word search.  I found nothing.  I did what I

> could  do.  I'm sorry it

> wasn't up to your standards.  But if your standards

> are so freaking high you

> should be more on the ball about it. 

__________

 

Whatever.  As I said before, I did a search and didn't find one.  I guarantee that if whoever someone logged it they didn't identify it properly in their log.  I also guarantee that SOMETIME between December 30th and the time that the locationless caches were logged the day before yesterday you had time to look at them, but didn't.  My guess is you even saw it but decided to screw people over just for fun.  You do that.  Have fun.  Oops.  You did.  And you did.  Whatever.

:D

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...