Jump to content

Manipulative cachers...


tazmyers
Followers 3

Recommended Posts

So I am new to the forums as I have just about had enough of the hassle one specific cacher gives me.

 

I wont name and shame unless others start saying I know exactly who you are talking about and i have the same problem also.

 

This cacher is just down right evil.

 

we have had issues with them in the past where we know they were using an alias cacher name to question one of our finds, recently we went to get one of their caches and boom, problems again. Incorrect listing/negligence to politeness. Encrypting of our log - then it gets worse.

 

We know that this specific cacher has several family cachers also and the cache that we got recently was within 0.05miles of a previous cache that was archived. The cache was archived after a family member AND this alias we have had problems with both jumped on the band wagon and thus got it archived. But within 4 days of this happening the cacher in question gets their cache published.

 

I might mention that this family member of theirs doesnt even live in the area anymore.

 

You might not see it personally everywhere, but this cacher is cyber-bullying.

 

Ganging up on a cacher to place your own cache there is just disgusting. Getting your family member to help create problems.

 

They arent a new cacher, they are well seasoned and with this you would have thought some knowledge would have been gained it to play this GAME.

 

But no, from this they have learnt how to manipulate and bully others which is really harsh.

 

Giving they are well seasoned, you would think they know how to place caches as well, but every single cache we have (and several other cacher freinds have logged) the co-ords have been out, and not just by a bit but a LOT.

 

The cacher has grandchildren who do caching also, and even one of their grandchildren have started lying about the position of a cache just so they can have a cache out there.

 

Why is this allowed and why does it happen?? We are all here for the same thing yet its cachers like this who make others feel insignificant.

Link to comment

I'm having a hard time following.

 

>boom,problems again.

 

Did the cache owner not like you log? What did you post that they didn't like?

 

>... The cache was archived after a family member AND this alias ...

 

Was it a cache of yours that was archived? Why was it archived - there must have been some reason they raised to the reviewer or cache owner?

Link to comment

I dont know what the cacher didnt like.

 

I wont state what I wrote because then you will know which cache i am talking about lol

 

the cache in question is something that would need questioning over its type anyway.

 

the manipulative cachers dauughter and the alias cacher that ive had a run in with the past are the ones who requested archiving of this specific cache.

 

Yes maintance should have been done, but the whole point of this seems as though "oh i want to place and publish a cache in that area, this one hasnt been looked after recently lets jump on the band wagon and get it archived so we can place our own cache here" type thing.

Link to comment

I dont know what the cacher didnt like.

 

I wont state what I wrote because then you will know which cache i am talking about lol

 

the cache in question is something that would need questioning over its type anyway.

 

the manipulative cachers dauughter and the alias cacher that ive had a run in with the past are the ones who requested archiving of this specific cache.

 

Yes maintance should have been done, but the whole point of this seems as though "oh i want to place and publish a cache in that area, this one hasnt been looked after recently lets jump on the band wagon and get it archived so we can place our own cache here" type thing.

 

Without giving us any information though we can't really advise.

showing us the log won't give away the cache just the log. we can then do the fun thing of looking for your log if we wish and then we get to see the cacher.

you're not naming and shaming we're figuring out who it is and can then try and advise

Link to comment

right what he/she is trying to say is they're having a problem with a cacher who is trying to get caches archived by getting their family to also complain about said cache so they can then place a cache in the same place.

 

this cacher also has problems with actually placing caches with the right coordinates

 

OP wants to know if anyone else has had any issues with this cacher and wants to know what the point of the cacher doing this is.

Link to comment

right ok

 

A) theres one cache that we have gotten recently that after we placed our log the cacher encrypted our log so it couldnt be read. without reason.

 

B)this cache that we have gotten recently has been placed within 0.05 miles of another cache that was that much away.

 

C) this cache was jumped on by 1) the manipulative cachers daughter who doesnt live in the area. 2) known alias of the manipulative cacher that decided one day to question of on my finds.

 

D)the manipulative cachers grandchild has caches out there that have been lied about the actual position of them.

 

E) the cache that was archived (yes should have been maintained, but when two people jump on the cache its difficult to get there - life gets in the way) - this was not a cache of mine.

 

The whole family seems to think they can lie their way through geocaching.

Link to comment

right what he/she is trying to say is they're having a problem with a cacher who is trying to get caches archived by getting their family to also complain about said cache so they can then place a cache in the same place.

 

this cacher also has problems with actually placing caches with the right coordinates

 

OP wants to know if anyone else has had any issues with this cacher and wants to know what the point of the cacher doing this is.

 

THATS EXACTLY WHAT I AM SAYING!!

thank you xx

Link to comment

right what he/she is trying to say is they're having a problem with a cacher who is trying to get caches archived by getting their family to also complain about said cache so they can then place a cache in the same place.

 

this cacher also has problems with actually placing caches with the right coordinates

 

OP wants to know if anyone else has had any issues with this cacher and wants to know what the point of the cacher doing this is.

 

THATS EXACTLY WHAT I AM SAYING!!

thank you xx

 

No problem.

 

we're in the same (ish) area (southern england) and i am currently trying to look through your caches or logs at the moment i can't see complaints on your caches. maybe you could give us a nudge in the right direction?

 

EDIT: just seen it's not on your caches. will go through the caches you've found :)

Edited by sparklefingers
Link to comment

right what he/she is trying to say is they're having a problem with a cacher who is trying to get caches archived by getting their family to also complain about said cache so they can then place a cache in the same place.

 

this cacher also has problems with actually placing caches with the right coordinates

 

OP wants to know if anyone else has had any issues with this cacher and wants to know what the point of the cacher doing this is.

 

THATS EXACTLY WHAT I AM SAYING!!

thank you xx

 

No problem.

 

we're in the same (ish) area (southern england) and i am currently trying to look through your caches or logs at the moment i can't see complaints on your caches. maybe you could give us a nudge in the right direction?

 

EDIT: just seen it's not on your caches. will go through the caches you've found :)

 

I have private messaged you :)

Link to comment

If a cacher lies about the condition of a cache to get it archived then provide photo proof to the contrary. Here in the US, unless there is a serious issue the Reviewers will usually disable 30 days before archiving.

 

If the CO is posting bad coords call them out politely in their logs. If they encrypt your logs I believe that is their discretion as CO. If the coords are significantly off then you may want to alert your Reviewer too.

Link to comment

If a cacher lies about the condition of a cache to get it archived then provide photo proof to the contrary. Here in the US, unless there is a serious issue the Reviewers will usually disable 30 days before archiving.

 

If the CO is posting bad coords call them out politely in their logs. If they encrypt your logs I believe that is their discretion as CO. If the coords are significantly off then you may want to alert your Reviewer too.

 

CO has been called by many cachers over their co-ords.

 

in their words, "maybe you should use a gps as it is more accurate than a smartphone".

Link to comment

I randomly selected a few of your found caches by random cache owners and see that all of them are quite minimal, just the number of the find. They've recently been editted to, example.

 

#447 tftc

This entry was edited by tazmyers on Saturday, 09 March 2013 at 18:40:49 UTC.

 

Is this because of the hassle you've been having?

Link to comment

erm excuse me.

 

10 out of 11 were edited because we put for example #447.... it gets confusing what number your on when your out in the field!!

 

not exactly any of your business why i edit my logs but hopefully that should satisfy your curiosity.

 

ps i am not talking about any of my caches being archived.

 

its not in relation to any of my caches found or placed.

Link to comment

I randomly selected a few of your found caches by random cache owners and see that all of them are quite minimal, just the number of the find. They've recently been editted to, example.

 

#447 tftc

This entry was edited by tazmyers on Saturday, 09 March 2013 at 18:40:49 UTC.

 

Is this because of the hassle you've been having?

 

no i am quite happy in posting what the cache was about should it be a story or an experience worth while talking about. you will see on a cache what it is i am talking about and understand that where.

 

for those who now feel the need to slate me for writing tftc. i have two children and 99% of the time i dont have the time to write a giant story..... thats just my thing. for caches that are fun and i enjoy i write about. x

Link to comment

Ive been going through most of it. was a cache that used to be in the same place as one of OPs recent finds.

 

the CO that has recently placed the new cache didn't actually place it recently. it was place back in september but only got activated recently. this is the one OP is on about.

 

http://www.geocaching.com/seek/cache_details.aspx?guid=a70bc42b-7746-4da0-972b-9238fc8ded6c

Link to comment

With all the overtly dramatic subterfuge added by the OP, it is really tough for me to get a grip on what advise they want from the community. For instance, when the OP mentioned, "Encrypting of our log - then it gets worse.", without seeing the log in question, there really is nothing to discuss. There are a host of reasons a cache owner will encrypt a log. Most of them are valid. Show us the log in question, and we might be able to help, or at least offer sympathy.

 

Then we have this:

"The cache was archived after a family member AND this alias we have had problems with both jumped on the band wagon and thus got it archived. But within 4 days of this happening the cacher in question gets their cache published."

 

Again, without details, all we can do is offer pointless speculation. In other instances similar to this, I've seen where a cacher placed a hide which turned out to be too close to an existing one, and since they liked the spot, they opted to keep it there and await attrition. This may be the case here. It seems like the archived cache had significant issues and the owner was unable or unwilling to do the bare minimum required to keep it alive? Again, just speculation, since you refuse to provide relevant details. Assuming this is the case, (a cache needing maintenance but not getting it), the owner could have at least posted a note explaining the circumstances behind their delayed maintenance. Every Reviewer I know recognizes that life happens, and if a cache owner at least shows they are trying, are oft willing to extend the grace period before pulling the trigger.

 

Perhaps the guy who placed the current cache saw that the obstructing one was in dire straights, and saw that the owner was doing nothing to correct it, so they posted a "Needs Archived", then submitted their cache when the deed was done?

 

The forums really are a great place to get advice for those problems that creep up in this interactive hobby, but to get sound advice we need details.

Edited by Clan Riffster
Link to comment

With all the overtly dramatic subterfuge added by the OP, it is really tough for me to get a grip on what advise they want from the community. For instance, when the OP mentioned, "Encrypting of our log - then it gets worse.", without seeing the log in question, there really is nothing to discuss. There are a host of reasons a cache owner will encrypt a log. Most of them are valid. Show us the log in question, and we might be able to help, or at least offer sympathy.

 

Then we have this:

"The cache was archived after a family member AND this alias we have had problems with both jumped on the band wagon and thus got it archived. But within 4 days of this happening the cacher in question gets their cache published."

 

Again, without details, all we can do is offer pointless speculation. In other instances similar to this, I've seen where a cacher placed a hide which turned out to be too close to an existing one, and since they liked the spot, they opted to keep it there and await attrition. This may be the case here. It seems like the archived cache had significant issues and the owner was unable or unwilling to do the bare minimum required to keep it alive? Again, just speculation, since you refuse to provide relevant details. Assuming this is the case, (a cache needing maintenance but not getting it), the owner could have at least posted a note explaining the circumstances behind their delayed maintenance. Every Reviewer I know recognizes that life happens, and if a cache owner at least shows they are trying, are oft willing to extend the grace period before pulling the trigger.

 

Perhaps the guy who placed the current cache saw that the obstructing one was in dire straights, and saw that the owner was doing nothing to correct it, so they posted a "Needs Archived", then submitted their cache when the deed was done?

 

The forums really are a great place to get advice for those problems that creep up in this interactive hobby, but to get sound advice we need details.

 

Its not that difficult to understand. the link to GC3XQ1M has been published.

 

That cache description was edited at 10pm last night, at 9.30 last night my log was encrypted. You can see it now plain as day - here I go in the log stating that I had two freezing cold children standing by the side of a river waiting for a QR reader to download on my phone - had i been told in the cache description that i needed a QR reader then I WOULD HAVE DOWNLOADED ONE TO SAVE TIME!!

 

i stated it would have been polite to say you needed this. When CO edited the description last night it didnt say specialist equipment would be required.

 

If you look for the cache sneaky beaky which was 0.05 miles away from it originally before it was published - it was high jacked by charlie lima and g and raggled robin.

 

Charlie lima and g is norfolk12's daughter - she also doesnt live in the area anymore to report on a needs maintance.

Raggled robin is an alias used by norfolk12.

 

Co-incidence that norfolk12 wants to publish a cache that she had placed there (8a) in sept yet in august sneaky beaky was placed there making it not possible to publish 8a.

 

so norfolk12s daughter and her own alias bullys down a cacher getting it archived and in the space of 4 days publishes her 8a cache because the one in question is no longer a problem!!!!!

 

Norfolk12s grandson - little fair bear - LFB has a lot of caches out there also. Once specific cache that is sat across the road from me isnt where it says it is. Stone pit park - a home to roost. It was somewhere fine, it was then moved, punblished then it had to be moved as area person castragli (sp) said it was to close to another cache. LFB then goes oh yes its moved back then - the cache is where it got moved to. not where he says it is.

 

This whole family of daughters, grandsons/daughters and alias's ANNOYS THE LIVING HELL OUT OF ME!!

 

they go round ruling our local area - her caches are shockingly out of co-ords (by 70ft at least one of them) yet when EVERYONE SAYS CO-ORDS ARE WRONG its us that should use a gps or a better smart phone to find the cache that she has placed!!!

 

In another instance, LFB logged a FTF on a cache that was published and missing within the same day then replaced the next with me and another cacher getting ftf and stf when LFB log stood at the top when we had just seen Norfolk12 replace that exact cache without her grandson!!!!!

 

Its like oh ive got to replace a cache - do you want FTF on it without doing the work on it scott??

 

Why should one family manipulate one caching area again!!!

Link to comment

This one? http://www.geocaching.com/seek/cache_details.aspx?guid=81c832ed-6455-4209-82b8-b9c68d8acef2

 

464 Feet away. If this is the one it appears the owner is no longer caching(or maintaining) I am all in favour of having these caches removed so that another can be put in place. especially a Multicache.

 

dont get me wrong i get as a placer also you dont maintain your caches then they will get archived.

 

but they jumped on the bandwagon to get the cache archived so they could place her own multicache/puzzle cache because they could! :(

Link to comment

Here's the thing...there's nothing anyone on the forums can do. You can let GS know about the situation, as well as the local reviewer, then put the whole family on your ignore list and cache elsewhere. I don't see any other choice for you--it's too bad, but all you can do is move on and cache elsewhere.

Link to comment

Here's the thing...there's nothing anyone on the forums can do. You can let GS know about the situation, as well as the local reviewer, then put the whole family on your ignore list and cache elsewhere. I don't see any other choice for you--it's too bad, but all you can do is move on and cache elsewhere.

 

I am fully aware there is nothing the forum can do, but giving that i thought this was a forum to discus geocaching - which i am doing, i thought i would get someones understanding of the situation instead of the - sorry no can do go moan and cache somewhere else that i am getting.

 

Can not one of you tell me that it doesnt seem suspicious of what that cacher is doing and their family.

 

Ps its easyer said than done caching somewhere else, but as it is we only have puzzle caches left where we live and have already done all of n12s caches.

Link to comment

Can not one of you tell me that it doesnt seem suspicious of what that cacher is doing and their family.

Regarding the archived cache, no, it doesn't seem suspicious in the least to me.

Cacher A is getting ready to place a multi.

Cacher B places and gets published a traditional in the vicinity of Cacher A's prospective spot, preventing Cacher A's cache from being published.

Cacher A waits and keeps an eye on Cacher B's cache, to see if it will eventually be archived, allowing them to then submit their cache.

Cacher B's cache goes several months without being found, including at least 2 DNFs from non-alias and non-'manipulative cacher's.

Cacher A logs Needs Archive, to bring what appears to me to be an abandoned cache to the attention of a reviewer.

Reviewer disables cache on behalf of Cacher B, and gives them fair warning to fix the cache or have it be archived.

Cacher B does nothing, so the reviewer archives the cache.

Cacher A then submits their cache and has it published.

 

All of this is completely normal and happens all the time. There's nothing manipulative going on here.

 

Regarding your other troubles with them, it sounds like there was some prior incident that caused animosity between you. Really all you can do is ignore them or try to address whatever issues you have between you.

Link to comment

Without passing judgment on any of the geocachers involved, let me just say that there are annoying geocachers out there. But I think you'll enjoy this activity a lot more if you try to not let their actions affect you very much.

 

If a geocacher's coordinates are bad, then I usually post alternative coordinates in my log to assist future searchers (and to help cache owners correct their coordinates, if they are interested). If the cache owner doesn't correct their coordinates, then you optionally can report that problem to the Volunteer Reviewer who published it. Another option is to simply not look for that geocacher's hides.

 

If a cache owner encrypts your log, then consider letting that slide. It's no fun getting into a dispute with another geocacher, and you're unlikely to win this battle anyway. You can still decrypt your log if you want to read about your experience in the future. Others might not bother to decrypt your log and might miss out on some helpful advice, but there's really not much you can do about it.

Link to comment

 

Its not that difficult to understand. the link to GC3XQ1M has been published.

 

That cache description was edited at 10pm last night, at 9.30 last night my log was encrypted. You can see it now plain as day - here I go in the log stating that I had two freezing cold children standing by the side of a river waiting for a QR reader to download on my phone - had i been told in the cache description that i needed a QR reader then I WOULD HAVE DOWNLOADED ONE TO SAVE TIME!!

 

 

I'm not understanding most of what's going on but I have to say I too would be a bit miffed getting to a stage and finding out I need a cell phone with a QR reader. I'd want to know this in advance. The special tools note and attribute is not enough information. To me that means....bring a multitool.

Link to comment

 

Its not that difficult to understand. the link to GC3XQ1M has been published.

 

That cache description was edited at 10pm last night, at 9.30 last night my log was encrypted. You can see it now plain as day - here I go in the log stating that I had two freezing cold children standing by the side of a river waiting for a QR reader to download on my phone - had i been told in the cache description that i needed a QR reader then I WOULD HAVE DOWNLOADED ONE TO SAVE TIME!!

 

 

I'm not understanding most of what's going on but I have to say I too would be a bit miffed getting to a stage and finding out I need a cell phone with a QR reader. I'd want to know this in advance. The special tools note and attribute is not enough information. To me that means....bring a multitool.

 

thats my point - the special tool note was added after my comment and log was made. x

Link to comment

This one? http://www.geocaching.com/seek/cache_details.aspx?guid=81c832ed-6455-4209-82b8-b9c68d8acef2

 

464 Feet away. If this is the one it appears the owner is no longer caching(or maintaining) I am all in favour of having these caches removed so that another can be put in place. especially a Multicache.

 

dont get me wrong i get as a placer also you dont maintain your caches then they will get archived.

 

but they jumped on the bandwagon to get the cache archived so they could place her own multicache/puzzle cache because they could! :(

 

The NA was posted by someone who found the cache 2 days before it was published. Perhaps another sock of the owner, who has a dozen finds, and was active for an entire 2 weeks? :blink: Perhaps they forgot their password for the other e-mail account. :ph34r:

Link to comment

That cache description was edited at 10pm last night, at 9.30 last night my log was encrypted. You can see it now plain as day - here I go in the log stating that I had two freezing cold children standing by the side of a river waiting for a QR reader to download on my phone - had i been told in the cache description that i needed a QR reader then I WOULD HAVE DOWNLOADED ONE TO SAVE TIME!!

 

The CO encrypted it because you gave away the secret of the required tool.

 

.. but I, too, would be peeved if I find a need a smart phone once I get to the cache.

 

Still, what if it wasn't a QR code app? What if it was a ladder, or a widget, something else you didn't have? What if it was in the bush you spent 30 minutes looking for? You know that any cache can turn into a long ordeal so don't drag your kids, out in the cold, without jackets, at night, to chase an FTF, if you aren't prepared to deal with the environment.

 

A lot of people here don't look favorably on the FTF chase so you won't get much sympathy about problems that center around that race.

Link to comment

That cache description was edited at 10pm last night, at 9.30 last night my log was encrypted. You can see it now plain as day - here I go in the log stating that I had two freezing cold children standing by the side of a river waiting for a QR reader to download on my phone - had i been told in the cache description that i needed a QR reader then I WOULD HAVE DOWNLOADED ONE TO SAVE TIME!!

 

The CO encrypted it because you gave away the secret of the required tool.

 

.. but I, too, would be peeved if I find a need a smart phone once I get to the cache.

 

Still, what if it wasn't a QR code app? What if it was a ladder, or a widget, something else you didn't have? What if it was in the bush you spent 30 minutes looking for? You know that any cache can turn into a long ordeal so don't drag your kids, out in the cold, without jackets, at night, to chase an FTF, if you aren't prepared to deal with the environment.

 

A lot of people here don't look favorably on the FTF chase so you won't get much sympathy about problems that center around that race.

 

i wasnt looking for a FTF on it, as my log explains i had half an hour to kill so we went and got it as it was down the road from my mums.

 

the whole point was it didnt state i needed a tool, and i was pissed i had to stand around waitingto get a qr reader when she could have politely stated that it was a required tool to find her stupid cache.

Link to comment

The NA was posted by someone who found the cache 2 days before it was published. Perhaps another sock of the owner, who has a dozen finds, and was active for an entire 2 weeks? :blink: Perhaps they forgot their password for the other e-mail account. :ph34r:

Nope. By comparing the GL codes of the "Found it" log and the "Needs Archive" log, they were both submitted on the same day. It appears they back-dated the "Found it" log, but mistakenly chose a date before the cache was even published, making what is likely a bogus log appear even more bogus.

Link to comment

the cache owner doesnt see it like that.

 

I am freinds with their daughter who i called at 11pm last night and explained everything i am trying on here, she has told her mum and she is fully aware that something is going on dodgy.

 

I can tell you now that charlie lima and g's log did not take place before that cache was published because mimozakon was FTF and then 5 mins after we were STF! so charlie lima and g never EVER found that log let alone discovered it was missing - an impromptu phone call from charlie lima and g's mother (norfolk12) could have gone - oh i have a cache around the corner that i now can publish because this one is there, log it and then say it needs archiving.

 

ps i have said before but charlie lima and g do NOT live in this area anymore! there is no need for them to come by and then check on a cache they have "already found" to then find the need to log it as a needs archiving x

Link to comment

the cache owner doesnt see it like that.

 

I am freinds with their daughter who i called at 11pm last night and explained everything i am trying on here, she has told her mum and she is fully aware that something is going on dodgy.

 

I can tell you now that charlie lima and g's log did not take place before that cache was published because mimozakon was FTF and then 5 mins after we were STF! so charlie lima and g never EVER found that log let alone discovered it was missing - an impromptu phone call from charlie lima and g's mother (norfolk12) could have gone - oh i have a cache around the corner that i now can publish because this one is there, log it and then say it needs archiving.

 

ps i have said before but charlie lima and g do NOT live in this area anymore! there is no need for them to come by and then check on a cache they have "already found" to then find the need to log it as a needs archiving x

 

I have no idea what you are trying to say. You really need to take the time to read what you write and compose well constructed sentences with proper punctuation. You first sentence is a run-on sentence that makes no sense. I'm not trying to be the grammar police but trying, without success, to understand you.

 

I can tell you are letting too many things bother you. Yes you were upset about the QR reader requirement with some justification. Even so, your log should not have mentioned the need for a reader; any complaints about deficiencies of the cache should have been sent in private email. Everything else about the cache is not your concern and does not impact your caching. Put it behind you and enjoy teaching you kids the fun of caching.

Link to comment

So I am new to the forums as I have just about had enough of the hassle one specific cacher gives me.

 

I wont name and shame unless others start saying I know exactly who you are talking about and i have the same problem also.

 

This cacher is just down right evil.

 

we have had issues with them in the past where we know they were using an alias cacher name to question one of our finds, recently we went to get one of their caches and boom, problems again. Incorrect listing/negligence to politeness. Encrypting of our log - then it gets worse.

 

We know that this specific cacher has several family cachers also and the cache that we got recently was within 0.05miles of a previous cache that was archived. The cache was archived after a family member AND this alias we have had problems with both jumped on the band wagon and thus got it archived. But within 4 days of this happening the cacher in question gets their cache published.

 

I might mention that this family member of theirs doesnt even live in the area anymore.

 

You might not see it personally everywhere, but this cacher is cyber-bullying.

 

Ganging up on a cacher to place your own cache there is just disgusting. Getting your family member to help create problems.

 

They arent a new cacher, they are well seasoned and with this you would have thought some knowledge would have been gained it to play this GAME.

 

But no, from this they have learnt how to manipulate and bully others which is really harsh.

 

Giving they are well seasoned, you would think they know how to place caches as well, but every single cache we have (and several other cacher freinds have logged) the co-ords have been out, and not just by a bit but a LOT.

 

The cacher has grandchildren who do caching also, and even one of their grandchildren have started lying about the position of a cache just so they can have a cache out there.

 

Why is this allowed and why does it happen?? We are all here for the same thing yet its cachers like this who make others feel insignificant.

 

I too am having a hard time understanding the whole problem. I suspect that at least part of it is the difference between "american" english and the across the pond version. At any rate, if I may cut to the chase: What do you think should happen to make the situation more tolerable for you?

Link to comment

So I am new to the forums as I have just about had enough of the hassle one specific cacher gives me.

 

I wont name and shame unless others start saying I know exactly who you are talking about and i have the same problem also.

 

This cacher is just down right evil.

 

we have had issues with them in the past where we know they were using an alias cacher name to question one of our finds, recently we went to get one of their caches and boom, problems again. Incorrect listing/negligence to politeness. Encrypting of our log - then it gets worse.

 

We know that this specific cacher has several family cachers also and the cache that we got recently was within 0.05miles of a previous cache that was archived. The cache was archived after a family member AND this alias we have had problems with both jumped on the band wagon and thus got it archived. But within 4 days of this happening the cacher in question gets their cache published.

 

I might mention that this family member of theirs doesnt even live in the area anymore.

 

You might not see it personally everywhere, but this cacher is cyber-bullying.

 

Ganging up on a cacher to place your own cache there is just disgusting. Getting your family member to help create problems.

 

They arent a new cacher, they are well seasoned and with this you would have thought some knowledge would have been gained it to play this GAME.

 

But no, from this they have learnt how to manipulate and bully others which is really harsh.

 

Giving they are well seasoned, you would think they know how to place caches as well, but every single cache we have (and several other cacher freinds have logged) the co-ords have been out, and not just by a bit but a LOT.

 

The cacher has grandchildren who do caching also, and even one of their grandchildren have started lying about the position of a cache just so they can have a cache out there.

 

Why is this allowed and why does it happen?? We are all here for the same thing yet its cachers like this who make others feel insignificant.

 

I too am having a hard time understanding the whole problem. I suspect that at least part of it is the difference between "american" english and the across the pond version. At any rate, if I may cut to the chase: What do you think should happen to make the situation more tolerable for you?

 

I did bullet point it above.

 

She wanted to understand why this family group of cachers are doing what they're doing.

 

This group of cachers got a cache archived (faster then it would of normally had been) so they could place their multi cache.

 

She also has been harassed about some of her finds by some of this group.

 

This group also place caches with bad coords or move the cache after being published closer to the area they wanted but couldn't have because it was too close to another one.

 

She wants to know if anyone else has had a Run in with these cachers also.

 

And a bit of a rant as she is upset.

 

I've spent most of the day looking at the caches and cachers and while they're not obvious in their posts but the fact that they've been upsetting the local cachers says something to me.

 

OP like I said to you, maybe it's worth talking to our reviews (as I'm sure our most common one is the same due to our area) and see what they say about things.

 

Edit because I've been smart phoned.

Edited by sparklefingers
Link to comment

<snip>

 

i have two children and 99% of the time i dont have the time to write a giant story..... thats just my thing. for caches that are fun and i enjoy i write about. x

I agree. "Giant" stories have been done to death, but if you could somehow work in the two kids WITH the giant... Sort of "Hansel and Grettel Meet Jack and the Beanstalk" treatment then maybe we've got something. :lol:

 

Now on topic... It's obvious that you've let this cacher get under your skin. It isn't worth the angst. Let it go. The cache that got archived deserved to be archived. The need for special tools got addressed shortly after you posted your log. Seriously, you should try to relax and enjoy the hobby. It's not worth getting upset over any of this.

Link to comment

As for the QR code thing, they put the cache live without ticking an icon for special tool, well we all make mistakes! but they corrected it immediately you mentioned it, so I don't see anything to get steamed up about there. They encrypted your log - so what? I could understand you getting upset if they'd deleted it but I don't see a problem with encrypting it, the log was still there for anyone to see if they were interested. As a matter of interest was it originally published with the field puzzle attribute that it now holds?

 

 

This group of cachers got a cache archived (faster then it would of normally had been) ...

 

I don't agree with that, the NM log was posted, the reviewer gave the usual (in the UK) 14 days notice to the CO to respond and they didn't, then it was archived after 21 days so nothing out of the ordinary there. Whatever the rights and wrongs here the CO is clearly not maintaining their cache so it's right that it's gone.

 

However having said that the whole situation does sound suspicious and there may be room to speculate how the cache disappeared :ph34r: due to the NM being logged by someone who isn't from the area and who also posted a seemingly faked found it log. If The A-Team are correct in their analysis of the two logs then either CL&G found the cache and then logged a NA (on the basis that it was missing) on the same day; or they just faked a find on the cache when they knew it was already gone; either way there's something not right there.

 

If this cacher is also placing caches at published co-ords and then moving them after publication into a spot where they wouldn't have been accepted then that's not right (it's happened before though!) and should be brought to the attention of the reviewer who published the cache(s) who should disable it/them.

 

On balance I think you might have been better putting this in the UK regional forum where you might have found some other cachers from the area who may have added some more local perspective.

Link to comment

Yes you were upset about the QR reader requirement with some justification. Even so, your log should not have mentioned the need for a reader; any complaints about deficiencies of the cache should have been sent in private email.

 

I completely disagree with not putting vital information in a log. A qr code reader is not a "field puzzle" or a TOTT, and if it's not mentioned in the cache description, I would also be very annoyed to find out that the cache can only be found with specialized equipment, which I don't have.

 

Since I read the logs on a cache, I deeply appreciate previous searchers including important information in their logs. It can be the deciding factor or whether or not we will attempt a cache.

 

I'm wondering if the reviewer had any idea of the qr code reader being necessary to find the final location. At the very least, the cache should have been published as an "Unknown" rather than a multi.

 

 

B.

Link to comment

As for the QR code thing, they put the cache live without ticking an icon for special tool, well we all make mistakes! but they corrected it immediately you mentioned it, so I don't see anything to get steamed up about there. They encrypted your log - so what? I could understand you getting upset if they'd deleted it but I don't see a problem with encrypting it, the log was still there for anyone to see if they were interested. As a matter of interest was it originally published with the field puzzle attribute that it now holds?

 

 

This group of cachers got a cache archived (faster then it would of normally had been) ...

 

I don't agree with that, the NM log was posted, the reviewer gave the usual (in the UK) 14 days notice to the CO to respond and they didn't, then it was archived after 21 days so nothing out of the ordinary there. Whatever the rights and wrongs here the CO is clearly not maintaining their cache so it's right that it's gone.

 

However having said that the whole situation does sound suspicious and there may be room to speculate how the cache disappeared :ph34r: due to the NM being logged by someone who isn't from the area and who also posted a seemingly faked found it log. If The A-Team are correct in their analysis of the two logs then either CL&G found the cache and then logged a NA (on the basis that it was missing) on the same day; or they just faked a find on the cache when they knew it was already gone; either way there's something not right there.

 

If this cacher is also placing caches at published co-ords and then moving them after publication into a spot where they wouldn't have been accepted then that's not right (it's happened before though!) and should be brought to the attention of the reviewer who published the cache(s) who should disable it/them.

 

On balance I think you might have been better putting this in the UK regional forum where you might have found some other cachers from the area who may have added some more local perspective.

The caches I've seen needs archive on have had 28 days notice on....

 

It all seems a little weird that that person that logged the needs archive is the child of the new cache owner.

 

Like I said I spent most of my day at "work" looking at the caches (works slow atm) and I am seeing links everywhere between certain cachers that have complaint on other cachers.

 

I was looking at one cache from the group and it had multiple dnfs by high find cachers and then a load of finds from a load. Of new cachers that seemed to only find caches by that group.

Link to comment
Guest
This topic is now closed to further replies.
Followers 3
×
×
  • Create New...