Jump to content

What do I do here?


DukeOfURL01

Recommended Posts

In one of my caches another user has logged a find, and used to log to completely talk trash about my cache, as well as give away the hide. My first instinct is to just delete the log, but I am afraid of that action being judged against me, so I have done nothing yet. My second instinct is to send a message to the user, asking them to change their log completely or else I will delete the log and that they have 24 hours to comply (but again, I have not taken any action)

 

The cache in question is: [/url]GC20J9B

 

 

What should I do here? This has me very upset.

Link to comment

You could delete the log and send them an email explaining it's because of the spoiler and invite them to relog without the spoiler. If you want to be a nice guy you can send them an email first asking them to edit the spoiler. But since it's a new hide that everybody is reading I'd probably delete it sooner rather than later.

There's nothing much you can do about the critical comments. Maybe include a polite comment in your email "I'm sorry the hide disappointed you."

Link to comment

Having found many caches placed by the logger in question I would just delete the log. I filter that users caches out of my searches because 25% of them are empty NONCAMO frosting cans tossed in the biggest poison oak bush with in 3 miles. 25% NONCAMO film canisters tossed out a car window at a guard rail. 25% NONCAMO quarter machine eggs in bird nests in poison oak. And 25% illegally placed caches (having to pull state park trail signs out of the ground to find) so ya she has NO room to say ANYTHING about anyones caches IMO

Link to comment

If I'm looking at the right log, you must have a very polite group in your local area. That barely ticked my angst meter compared to many others I've read. I would have treated the log as constructive criticism of how I might have done a better job in placing and concealing the cache.

 

When I leave a log anything close to that in negativity, I always take care to end by saying "Still, I do thank you for getting me out and about by hiding a this cache for me to find." A thank-you can go a long way.

Link to comment

Has the spoiler been removed already, 'cuz I don't see one? It's just another log. I'd shrug and move on. It's not a big deal that one person didn't like your cache and said so.

 

By the way, unless the hide is truly exceptional, when I see a spoiler in an old, well established cache's log, it strikes me as a mark of maturity. For the first couple years, a cache can fly under the radar, but after 4 years, I start imagining that "everyone" knows where it is, and after that it only has to keep its secrets from muggles.

Link to comment

Seriously, though, her log was rude. You are under no obligation to camo your cache and even if the description wasn't updated, that's no excuse for her rudeness. I've found some crappy caches, but I can usually think of something nice to say or at least just a TFTC.

 

As for 'giving away the hide'...is this meant to be a tricky hide? If not, I wouldn't care too much about spoilers. I've received a number of logs on my caches with spoilers especially photos. I don't care much, unless it's meant to be a tricky hide.

 

As for what to do about it, you can either ignore it, encrypt it or send her an email asking her to change it. I wouldn't give her a 24 hour ultimatum, just say 'Could I ask you to change your log to remove the spoiler i.e. the bit out it being in a hole in the ground. I also was kind of upset to receive your criticism of my cache. I agree I didn't put alot of effort into it, but not all caches need to be specially camo'd. Sometimes it's more about bringing people to the area than the cache container itself. Thanks'.

Edited by The_Incredibles_
Link to comment

Quite the contrast between thompsonworld's log and the one in question. I'd leave the log (as others have said, karma will work here), go fix (camo) the container, and everything takes care of itself.

 

A log like that would hurt my feelings, too. But when a CO places a cache, they open themselves up for opinions.

Link to comment

If I'm looking at the right log, you must have a very polite group in your local area. That barely ticked my angst meter compared to many others I've read. I would have treated the log as constructive criticism of how I might have done a better job in placing and concealing the cache.

 

When I leave a log anything close to that in negativity, I always take care to end by saying "Still, I do thank you for getting me out and about by hiding a this cache for me to find." A thank-you can go a long way.

 

I agree with the creepy looking frog/hamster hybrid. She could have been more polite, but the comment wouldn't have made me twinge at all if it were on one of my caches.

Link to comment

I agree with the folks that say it's negative. She says the cache stuck out like a sore thumb. Maybe the last finder left the cache exposed to make it easier to find - maybe because people are reporting that the cache is 40 feet from ground zero. I had to read her log 4 times to see where there might be a spoiler..."container in a hole". I'm not sure that would help me much. Someone earlier said "It really is an "obvious" location (or as obvious as you can get in the redwoods!)", and "Mother Faulker was 40 feet from GZ! I looked right next to it but had seen a spot or two that looked more likely a bit away from GZ and went to investigate", those seem like more of a spoiler, but important information without a hint provided and coordinates that are off because of a thick canopy of trees.

Link to comment

Having found many caches placed by the logger in question I would just delete the log. I filter that users caches out of my searches because 25% of them are empty NONCAMO frosting cans tossed in the biggest poison oak bush with in 3 miles. 25% NONCAMO film canisters tossed out a car window at a guard rail. 25% NONCAMO quarter machine eggs in bird nests in poison oak. And 25% illegally placed caches (having to pull state park trail signs out of the ground to find) so ya she has NO room to say ANYTHING about anyones caches IMO

 

MBH and I are in the same boat here, except for our opinion on what to do. I've also found many of said cachers really poorly placed and/or maintained caches, and had run ins with her regarding her hides, my logs, my placements, etc....

 

She has the attitude of being the best local cacher there is. Whatever that means. It wouldn't surprise me if she went to find Duke's cache just to find some reason to talk it down, given the history I know these two have.

 

Leave the log there Duke. I've slept on it after the message I sent you last night, and deleting her log will only A) Satisfy whatever desire she has to irritate you, and B) give her the chance to log it again with some other negative comments about why you may have deleted her log. It's certainly not the worst log she's written on a cache, so maybe an email asking her to change it would be about the only thing I might (MIGHT) do in this circumstance.

Link to comment

I agree with the folks that say it's negative. She says the cache stuck out like a sore thumb.

I guess this is what I'm missing. If the cache sticks out like a sore thumb, why is it negative to say it sticks out like a sore thumb? If I think a hide needs more thought, what's wrong with saying it needs more thought? The more I read the log, the more it seems only slightly abrasive, hardly even raising to the level of rude. To be considered rude, I'd need evidence that these comments are not accurate, and I don't see the OP actually making that case. (The OP doesn't mention whether they visited the cache to see if there really is a problem they don't know about, by the way.) Sure, the log is accusatory, and that's a bad way to write a log, but surely someone that's been hiding caches for 5 years has gotten used to being blamed for every little thing wrong with a cache regardless of whether the problem is something under their control.

 

And more than that, if I had a cache out in the middle of a forest where I knew and stated myself that tree cover reduced the accuracy to 25' -- that's 50' total, when you add my GPSr's error to the error of the seeker's GPSr -- I'd want people to put as many hints in the logs as they could cram in. Well, actually I'd put the information in the description myself, and something way more revealing that "it's in a hole" in an area that sounds like it has holes everywhere.

Link to comment

I agree with the folks that say it's negative. She says the cache stuck out like a sore thumb.

I guess this is what I'm missing. If the cache sticks out like a sore thumb, why is it negative to say it sticks out like a sore thumb?

 

Oops, the way I wrote that it did seem like I thought the sore thumb comment was negative. Perhaps a little abrasive but not all that bad. If it's true, it's true.

 

Overall, I'd say it was a negative post but not overly negative or rude. I looks like it's interpreted as overly rude because the OP and other cachers in that area have met the cacher and find her abrasive.

 

To be considered rude, I'd need evidence that these comments are not accurate, and I don't see the OP actually making that case.

 

I agree.

Link to comment

A few years back I received this response to finding my cache:

 

"Unfortunately have to say, that this cache is one of the worst I have ever found. Nothing to see, only forest full of rubbish . I think there are more beautiful places in Canada which deserve cache."

 

I of course did not delete the log, and was more amused than offended. However, when a CO deleted my log once, I was more offended than amused.

Link to comment

In one of my caches another user has logged a find, and used to log to completely talk trash about my cache, as well as give away the hide. My first instinct is to just delete the log, but I am afraid of that action being judged against me, so I have done nothing yet. My second instinct is to send a message to the user, asking them to change their log completely or else I will delete the log and that they have 24 hours to comply (but again, I have not taken any action)

 

The cache in question is: [/url]GC20J9B

 

 

What should I do here? This has me very upset.

i would delete the log, if the person is not a premium member I would move the cache and make a premium member cache

Link to comment

<I'm taking off moderator hat since I don't moderate in this part of the forum. The opinions below are my own, and not reflective of the moderating team of this portion of the forum.>

 

When I suggested implementing some type of metric to show better-than-average caches, I was inundated with comments of "just read the logs". People constantly said that reading the logs was one of the best ways to determine if a cache is worth the effort/time for the act of seeking. If have very precious little time for GPS adventures, and there are certain types of caches that I really don't think I would enjoy. Even if I weed through the caches by type, size and rating scales, if there are issues of hiding style that could present problems (like a ziplock in a decaying tree, etc.), I'd just as soon avoid it. So they said "read the logs".

 

But people can't seem to post their own opinions in logs. Cache owners seem to be quite defensive of their own hides, and any criticism seems to be taken as a personal affront to the person placing the cache. Instead, I believe cache finders should be entitled to their opinions and the ability to express them. However, in this case I believe the opinion could have been stated in a more diplomatic way. But if this log is to be believed at face value, there are some take-away suggestions: The camo might be ill-suited to the location, leaving the cache readily spotted by muggles, and potentially open for being taken as trash.

 

Rather than getting defensive and wishing to delete the offending log (thus escalating the matter which would almost always follow in further escalation), I would suggest reading facts out of the statement, and consider making a visit to the cache to see if there is any way to improve upon the placement and protect the longevity of the cache.

 

<heading back to my moderating corner in Getting Started and How Do I?>

Link to comment

The cache is in an area of the forest that has about 40' accuracy. The lack of accuracy is the only thing that makes the cache even remotely difficult.

Just to make sure we're clear about this, 40' accuracy is way more then "remotely difficult" in a forest. That means that your cache could be anywhere in a 5000 square foot area. And since your reading could have been 40' off and my reading could be 40' off in the other direction when I go to look for the cache, I'm going to have to search 20,000 square feet to find your cache in the absence of any hints. That's a third of a football field. With trees and who knows what kind of undergrowth to search in and around. I'm having a hard time imagining how "in a hole" would spoil a hide with those kinds of parameters. Besides, the description says you intended this cache to be quick and easy, so why are you worried that the next few seekers will know to limit their searches to holes? Are you worried that might make it quick and easy?

Link to comment

I slept on it, and I've decided that I'm not going to do anything. I'm just going to let it stand and hope that will reflect on the person, but I am going to point it out to everyone I can think of...

I've read some of her other logs. Comments like in your log are not unusual. She seems to be binary, say all is fine and the cache is good or she has to find fault with the cache in some matter. She seems to be a cache cop to me.

Link to comment

Generally, if a cacher makes a rude comment in his/her log, I leave the log. It shows how ignorant that cacher is. Let others judge her/him by the logs. (Good example: "What do you mean? I have to post a webcam photo for a webcam cache?!? I'm going to ignore all webcam caches." Go for it!)

On the other fin (as someone has mentioned) I do not like having my rude comments deleted. "Is this really family friendly with people having sex in the parking lot of the porn store?" That shows my attitude. Take it as you will. Or: "The rats here are larger than many small dogs."

Leave the logs for others to judge.

Link to comment

I am the one that wrote the log (thank you to a cacher who saw this and alerted me to the thread). I did write the log and if it was taken as RUDE well thats how it was taken. What I wanted to write was that i was disappointed in this hide from this person because he is capable of much better hides and CALLS OUT THESE KINDS ALL THE TIME. I believe that this could be a replacement and I believe that I did say that in my log (if I did not I had intended to do so) I also intended to send the CO an email alerting him of said cache and its lack of camo. ALSO i noted that I did hide it better than i had found it. Now YES I have deleted logs for my own reasons and I am allowed to do so. Just as Anthony you are allowed to bash my log all you want. I do believe that there are a few in this thread that said that my log was not rude to them and they have seen worse. Well Thank you to them. I did not give away your location. I did not give away your hide. I simply stated that it stuck out like a sore thumb and I did my best to hide it better. I believe that you are still mad because I made a find while you were there and got the log signed and replaced a cache that you still havent found all under your nose. Thats fine you have the right to still be mad. I have the right to not find any more of your caches. Either way you want this to play out is just fine with me....its just a GAME! Dont pick up your crayons and go home and then complain that some are broken. If anything you should be glad that I brought this cache to your attention so that you can go and actually check on it in a timely mannor and make it a cache of your shall we say quality? Rather than the white film canister at the base of a tree in the open that it was before I rehid it.

Have a fantastic day!

Link to comment
...

But people can't seem to post their own opinions in logs. Cache owners seem to be quite defensive of their own hides, and any criticism seems to be taken as a personal affront to the person placing the cache. Instead, I believe cache finders should be entitled to their opinions and the ability to express them.

...

 

Agree completely here. In my own not-so-gentle way, I would say that if you are not willing to accept some negative logs on your caches then you shouldn't hide them.

 

I don't blame the CO for his emotional reaction. The key is to get over it and realize that you can use the feedback to make your caches better.

Link to comment
...

But people can't seem to post their own opinions in logs. Cache owners seem to be quite defensive of their own hides, and any criticism seems to be taken as a personal affront to the person placing the cache. Instead, I believe cache finders should be entitled to their opinions and the ability to express them.

...

 

Agree completely here. In my own not-so-gentle way, I would say that if you are not willing to accept some negative logs on your caches then you shouldn't hide them.

 

I don't blame the CO for his emotional reaction. The key is to get over it and realize that you can use the feedback to make your caches better.

To expound a bit with my own intemperate thoughts;

If you don't want negative logs, hide great caches.

A film can at the base of a tree has lame written all over it.

Link to comment

In one of my caches another user has logged a find, and used to log to completely talk trash about my cache, as well as give away the hide. My first instinct is to just delete the log, but I am afraid of that action being judged against me, so I have done nothing yet. My second instinct is to send a message to the user, asking them to change their log completely or else I will delete the log and that they have 24 hours to comply (but again, I have not taken any action)

 

The cache in question is: [/url]GC20J9B

 

 

What should I do here? This has me very upset.

 

Take it in stride Duke... I've been much harsher in my logs - In fact, I really PO'd the logger in question once with a comment about a particular use of the hint field.

 

It happens.

 

Personally? If I knew one of my caches was not cammo'd when it should have been, I would have fixed it. If one of mine was placed 40 feet off? I would have disabled it and fixed it immediately! Placed in 2009? you should have fixed that YEARS ago! 40 feet off is totally unacceptable for a traditional hide.

It's your call but I really didn't find her log all that bad - yes I read the original but we just got home from a freaking awesome weekend so I'm only now replying.

 

have fun!

Link to comment

In one of my caches another user has logged a find, and used to log to completely talk trash about my cache, as well as give away the hide. My first instinct is to just delete the log, but I am afraid of that action being judged against me, so I have done nothing yet. My second instinct is to send a message to the user, asking them to change their log completely or else I will delete the log and that they have 24 hours to comply (but again, I have not taken any action)

 

The cache in question is: [/url]GC20J9B

 

 

What should I do here? This has me very upset.

 

OMG!! I can't help but to laugh!!! Her current log is (IMHO) FAR worse than the original one!!!

Link to comment

It's not 40 feet off. The GPS has accuracy of about 40 feet here, like I said, I think it's lying though. When I visit this one about once a year, somehow I still manage to zero in on it.

I feel the container doesn't need camo, because it's sufficiently dark at this place, but also it's not meant to be a hard hide in the first place.

Edited by DukeOfURL01
Link to comment
...

But people can't seem to post their own opinions in logs. Cache owners seem to be quite defensive of their own hides, and any criticism seems to be taken as a personal affront to the person placing the cache. Instead, I believe cache finders should be entitled to their opinions and the ability to express them.

...

 

Agree completely here. In my own not-so-gentle way, I would say that if you are not willing to accept some negative logs on your caches then you shouldn't hide them.

 

I don't blame the CO for his emotional reaction. The key is to get over it and realize that you can use the feedback to make your caches better.

To expound a bit with my own intemperate thoughts;

If you don't want negative logs, hide great caches.

A film can at the base of a tree has lame written all over it.

 

If it really is a film canister at the base of a tree in a forest listed as a small (not a micro) with no hint and 40 foot descrepancy, I would have had a very hard time not letting others know about it in my log and a very hard time not letting my disappointment show.

Link to comment

In one of my caches another user has logged a find, and used to log to completely talk trash about my cache, as well as give away the hide. My first instinct is to just delete the log, but I am afraid of that action being judged against me, so I have done nothing yet. My second instinct is to send a message to the user, asking them to change their log completely or else I will delete the log and that they have 24 hours to comply (but again, I have not taken any action)

 

The cache in question is: GC20J9B

 

What should I do here? This has me very upset.

 

OMG!! I can't help but to laugh!!! Her current log is (IMHO) FAR worse than the original one!!!

 

ROTFL!

Link to comment

It's not 40 feet off. The GPS has accuracy of about 40 feet here, like I said, I think it's lying though. When I visit this one about once a year, somehow I still manage to zero in on it.

I feel the container doesn't need camo, because it's sufficiently dark at this place, but also it's not meant to be a hard hide in the first place.

 

NO it was sitting there on top of the pile not hid at all...that was the point.

Link to comment
...

But people can't seem to post their own opinions in logs. Cache owners seem to be quite defensive of their own hides, and any criticism seems to be taken as a personal affront to the person placing the cache. Instead, I believe cache finders should be entitled to their opinions and the ability to express them.

...

 

Agree completely here. In my own not-so-gentle way, I would say that if you are not willing to accept some negative logs on your caches then you shouldn't hide them.

 

I don't blame the CO for his emotional reaction. The key is to get over it and realize that you can use the feedback to make your caches better.

To expound a bit with my own intemperate thoughts;

If you don't want negative logs, hide great caches.

A film can at the base of a tree has lame written all over it.

 

If it really is a film canister at the base of a tree in a forest listed as a small (not a micro) with no hint and 40 foot descrepancy, I would have had a very hard time not letting others know about it in my log and a very hard time not letting my disappointment show.

 

That is exactly what it was... and not up to the level of caches that I have come to expect from the Duke. hence the point of my log which I have now erased and replaced with the cachers cop out log TFTC...which I HATE by the way because I go to some effort to place a cache and to get a TFTC is like peeing in a cemetary just not ok. But thats what I shall from this point and time sign on Sir Dukes caches so that I dont get made FAMOUS on a message board... flattery I guess???

Link to comment

In one of my caches another user has logged a find, and used to log to completely talk trash about my cache, as well as give away the hide. My first instinct is to just delete the log, but I am afraid of that action being judged against me, so I have done nothing yet. My second instinct is to send a message to the user, asking them to change their log completely or else I will delete the log and that they have 24 hours to comply (but again, I have not taken any action)

 

The cache in question is: [/url]GC20J9B

 

 

What should I do here? This has me very upset.

 

OMG!! I can't help but to laugh!!! Her current log is (IMHO) FAR worse than the original one!!!

 

 

I agree Zop I dont like to use the "cacher cop out" log of TFTC but I dont want to be branded a Cacher bully by the Cache Police either! :)

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