Lazyboy & Mitey Mite

Hello, Permit me to note two facts for the record. The first fact is that the history of guideline changes is as follows: 1. The guidelines were revised in mid-February 2005. 2. The guidelines were revised in November 2003. I could go back further, but hopefully most will see my point. Second, please note what the reviewers have said about suggested solutions when concerns under the cache saturation rule have been identified. In the case at issue, a 20-stage multicache was not the solution suggested. Or in the case I've described here in Pennsylvania, I worked with a hider to make what I regarded as minor tweaks to an eight-cache series. Five stood well on their own, but when combined with three micros clustered nearby in a cemetery, this raised saturation concerns. I worked with the hider to transform the three micros into a multicache ending with an ammo box in the woods behind the cemetery. It is getting great reviews and the overall experience of the five standalone caches plus the multicache as a "finale" seems to be quite positive. There are any number of ways to address the saturation issues as they are identified. Each case will vary a bit due to the unique characteristics of the local area, and the pattern of hides submitted for review. Keep messing with it. It honestly doesn't matter how many you chase away with your changes because new ones are coming in all the time. I've been doing this four years now and I don't like what I'm seeing. .25 miles is the new rule, what will it be next year? Any ideas?

It's getting silly with these monthly revised rules. I laughed at the suggestion of a 20 stage multi. Multils around these parts die a lonely death. I certainly won't spend an entire day or weekend to log one. I'm sure others will but at least I'm not crying for a ban on multis. My suggestion is to quit screwing around with a perfectly good game. It's not as good as it once was and I don't see it getting better any time soon.

So who do I need to sleep with to get my picture on there?

missem

I notice there are quite a few new freshie tribute caches out there. I thought I'd add mine to the collection.... Watch Out For That TREEEEEEEE

Context? You claim I called you a crybaby and worse because of context? You never have logged a single cache of mine and I was talking about a user who had. Good grief.

Jefferey in your area it was a plunderer that went through and ripped off about 100 caches. The good news is that there are a lot of new caches around your valley now.

I didn't call you a crybaby, I called another unnamed user a crybaby. I didn't call you a control freak, you yourself said you didn't use the SBA button. I called you an idiot? I called the cacher who logged the whiney log on my cache an idiot. You have taken everything personally and then accuse me of breaking forum rules. But it's curious how you would take my post and apply it to yourself. Good grief man, give it a rest. All I did was disagree with you. Doesn't mean I called YOU names or even dislike you. You know why so many people don't like these forums? You really want to know why? Naw, you'd take it personally again.

That SBA button certainly appeals to control freaks I've discovered. I once had a crybaby complain about a cache in the guardrail because it was on a busy road and there was no parking close by. The coordinates were accurate and it took you to the guardrail. You had to park safely about 200 yards away. The idiot parked where it was dangerous and then complained about it. You could approach the cache and keep the guardrail between you and traffic but you'd think I was a criminal the way he went off. I didn't delete his log, instead I allowed others to see what an idiot he was. Umm, if you determined it's dangerous why did you spend so much time looking for it? We need rules to protect you from yourself? Maybe you could try to police yourself instead of asking GC.com to do it.

What the heck is a lawn anyway.

If I recall correctly Logscaler volunteered you to mow the lawn one weekend and me the next. To save us both some trouble and travel time I suggest we each be responsible for 6 month at a time. I'll take the period of October-March and you can have April-September. Oh what the heck, I'm a nice guy and I'll take September too and only make you take 5 months. Logscaler can volunteer me all he wants but he'll have to do my share for me. Or you can have all the shares yourself, I'm generous like that

He was released and is home now. Bufford is mowing his lawn for him.

If I hate I-5 is in the name it will show up here, I wish all the I-5 caches had such a name in it as it would sure be easier to find. I Hate I-5

For me a simple thank you works every time. I feel no need to trash anyone based on my opinion of their cache. Hey it got me out of the house and I added one to my numbers. you guys are too much. a forum full of judges.

The intent was to notify, a reaction after a related cache was disapproved was to complain about overly strict attention to guidelines. And your whine was duly noted.

Actually you'd be surprised how much flack I would have taken for listing it. As it was submitted it was not listable, make it fit the guidelines and I can take another look. Did you let the submitter know what they had to change? There are some guideline rules regardless that would be broken, such as a two week advance notice, not possible for someone visiting a hopsital in an emergency situation. It also would have run more than one day. Would you be willing to break those rules or would the fear of flack be too overwhelming? Don't worry about it, the locals in Eugene have taken care of it. They used their forums to spread the word. A small forum over there has nearly 1000 hits and is 3 pages long. The forums here have a few messages and around 300 hits. Not as many people use the gc forums as you might think. His logbook has many many signatures already. No thanks to these forums or the site. I recall a guy getting arrested a few years ago for hiding a cache in a bad place. His court date was turned into an event and it was approved. Things have sure changed haven't they and I don't think for the good. Personally if I were a mod I would have approved it, I would have made the changes required myself in order for it to be close enough to the rules to reduce the amount of flack headed my way. It would have been the right thing to do.

Except for the fact that I read this thread and the one on the EVC boards. So you checked around other theads on other forums. Well that's spending your time wisely. You take too much of this too seriously. This would have been a kind hearted thing to do for Freshie, instead you are just toeing the line rather than doing what is right. I have a feeling you wouldn't have gotten into trouble if you had approved this event cache.

You can spend an hour averaging but if you have a lousy signal you'll be way off. It's about a strong signal, if there isn't one, I don't hide there.

Well for some the letter of the law is more important than the spirit of the law. They'll be fine, it's just a shame.

Very dissapointing that our PTB couldn't bend the golden rules a bit to allow a cache event to be held in Jim's room during his extended stay. Sometimes the spirit of the event is more important than holding fast to rules. It would have been the right thing to do especially since Jim and Tara are a true geocaching couple who went caching on their first date and even held their wedding as a caching event.

He's a wreck for sure but current posts from the thread over there suggest he may only have a 30% chance of requiring surgery. Jim and Tara are really great people. It's a shame stuff like this happens to nice guys.

There is a thread in the Eugene group about Fresh_Meat and his accident here The Thread Lots of unanswered questions now but hopefully he'll come out of it good.

I always thought that long winded rambling have nothing to do with a hint type of hints were silly but, it doesn't bother me to the point that I want more rules.

There are some nice people over there.

Personally I haven't done one I consider lame.