Mike&Lily

We are going to try and get some cachers down from the north island. It would be fantastic if you could do a cache machine event in the Comox valley

It looks so far that there just isn't enough demand to produce a coin yet. A quick look with project-gc and I see that there are only 35 people who would qualify for this award in North America. We are extremely fortunate to have this geocacher in our community, I may have to buy a 600 and a 400 hide coin if I can't find the 1000.

We have a cacher in our community who has placed 1000 unique geocaches and we would like to find an achievement coin to celebrate this. Does anyone know wher I can find one?

Not too sure that I agree with all of the threads, but I have to admit that I have learned how to correct my incorrect logs and how to lock in my milestones. I started this thread not because I lost a smiley, but the fact that I hiked up a mt top to view a historical plane crash site, not to have my milestone changed to a micro on a mailbox. It is true that it was my fault and not the cache owner. Do they have the right, absolutely, not disputing that fact. Most of us have noticed that these mistakes are made as newbies and in our case there was no exception. It is odd that even now I have been reluctant to delete a newbies double log as I feared I might offend them and scare them away from the sport, but better now than their 5000 th find.

You are absolutely correct and we do not dispute this fact. We have truly been off by one cache all these years, but I will add this for our 5000th cache we chose to climb a mt and find the wreckage of an old plane. Quite a hike and I'm sure that I could have done a drive up to prior to this long hike had I been informed 4.5 years ago of the error that we had made oh so long ago.

Recently we had a cache log deleted because we had unintentionally logged a smilie twice No big deal right! Unless of course it happened on a cache that had been archived for over a year and and the duplicate log was written 29 june 2008 gc1bx6r So our question is this when should you delete a duplicate found log? We do it right away . We can only assume that duplicate found log deletions normally occur shortly after they happen I guess we have to appreciate the lengths that the cache owner went to in checking the archived cache and going back 4 1/2 years so that they could rectify our mistake Though we do think that may have been more helpful when the error occured and when we had just been caching a few months and we had not logged so many milestones. Now it just seems like someone with an axe to grind Your thought on this matter would be appreciated Mike Lily

I was just checking out creative videos on this site and actually watched a video with a very creative birdhouse screwed to a tree so if this is so against the guidelines why is it there. Sending a mixed message.This makes me think that these types of caches are approved .watched another that extends at least 2 ft into the ground with only the top exposed looks buried to me. both of these caches are variation of the same type that got this guy into trouble . why are they being showcased on this site if they violate guidelines

I'm hardly perfect, but when I find out that I break a rule in any place in my life, I admit to it. But I'm glad you noticed my rock hard booty. Ive been working out lately. thats some pretty hard talk. hope you got pics to back it up .lol!

it seems to be way to easy to cause trouble for someone you have a conflict with. It would be great if all that crap stayed out of caching but that is too much to hope for . The term guideline seems like a much more flexible word wish people were the same way.

From one of your logs on the cache page: One point I'd like to make about that, is that if HailHoll was very careful to not break any guidelines, there wouldn't be much that this vendetta holder could do about HailHoll's caches, is there? It seems you are a doglover by your pic. maybe you wouldn't feel like that if you memorial cache to your beloved pet was going to get removed because the bottom half was in the ground and all you had to do was lift the lid which to access the cache but apparently it qualified as buried Another grey area lots of caches out there like that but if someone has a bone to pick with you watch out Maybe he wouldn't feel like he had to follow the rules if he placed a cache that broke the rules that was for his favorite dog. What!?!?!? So far this is just complaining that people are getting caught for breaking the rules, and trying to justify it because they don't like the rule. Now you throw a guilt trip on somebody? FFS. sorry didn't mean to throw you a guilt trip that was the pre nail event this is the nail that broke the trees back lol! Anyhow yes this was for his deceased dog at the last cache that they found together and it was a memorial cache must've been his grief that blinded him to the fact that someone would take offence that a foot of dirt was removed Nice to see that soo many people never break the rules and are such hardasses. BTW; for all you perfect people out there show me the nail holes .I always thought the last perfect person got crucified!

From one of your logs on the cache page: One point I'd like to make about that, is that if HailHoll was very careful to not break any guidelines, there wouldn't be much that this vendetta holder could do about HailHoll's caches, is there? It seems you are a doglover by your pic. maybe you wouldn't feel like that if you memorial cache to your beloved pet was going to get removed because the bottom half was in the ground and all you had to do was lift the lid which to access the cache but apparently it qualified as buried Another grey area lots of caches out there like that but if someone has a bone to pick with you watch out

Wow George sure has stirred up the hornets nest anyhow here is the cache GC3MVY9 at the center of the controversy. This was a great cache and yes it may have broken a guideline but more than that the sore point for our local community is that this cache which is situated out in the woods on crown land was targeted by another cacher not because it broke guidelines but because of an ongoing feud with another cacher who is specifically using the rules for their own personal vendetta against the CO. Within a few hours of being published this cache was compained against but the complainant did not log their complaint on the cache page just sent out a complaint to the reviewer to get the cache removed . This enabled the person to stay anonymous and the feud is destroying the local caching community. The collateral damage is already starting with our most prolific cacher disabling 17 of his 255 hides because of tiny rule violations.( i.e. screw used on a burned out stump) And yes there are many great caches out there that violate the rules in one form or another. If nails or metal were going to hurt the trees around here than we wouldn't have any left. Alot of the caches here are on old logging roads and mining areas. we have seen numerous ones growing with rebar sticking out of them giant spikes and huge metal cables and some growing out of old vehicles and buildings. The trees and the enviroment have way more to fear from the polluters who travel miles on the backroads to dump their garbage. There are several caches around here that involve using water to retrieve the cache they are all screwed into trees but nobody complained and all these have been done by the person who complained about this cache so quickly. So I guess in a longwinded roundabout way what I am trying to say is that it is way too easy for a cacher with a grudge to use the geocaching guidelines to carry out a personal vendetta. If you are going to complain about a screw in a tree than complain about them all not just a cache by a specific cacher because you are holding a grudge. And for you people who are not local if you saw half the stuff we saw that was hurting trees around here you wouldn't worry about a teenie weenie screw. Lily