I would agree - there are some teams that spend lots of time maintaining their caches. There are many that don't. I would think the answer would be more self maintained by the finders for those teams that do not maintain their caches. I find that many do not post no finds. If we all did that, simply by reading the logs, other cachers would know there might be a problem and not waste the time to go there. I know for my caches, if there is a no find, I check on it and post a note letting everyone know that all is ok. So, how do you convince chachers to log the no finds, post notes, and send e-mails to the owners? It seems that some think a no find is bad. I think its courtesy to the general caching community. Tamo Scott Wood wrote: > At 08:14 PM 4/4/2003 -0700, you wrote: > >> so what should be done when you find a cache that the owner hasn't >> fixed after being plundered? I mean say 2 teams visit the site a week >> apart both stating that the cache is in diss repair or missing and >> the cache owner hasn't responded to any emails or postings to the >> matter??? then what would be appropriate time for fixing a cache??? > > > I don't know if there is a good answer for that. I guess it would > have to be case to case. Let's assume that one of my caches was > plundered in late Jan. I would not have been able to taken care of it > until late Feb. since I was on an unexpected trip to North Idaho for a > family crisis. Not only was I 1500 miles from my cache, but I had > terrible internet connectivity while there, and could hardly check on > my e-mail. > > Obviously I would want to fix my cache when I arrived back in Tucson, > but 1 week would hardly be enough time. On this particular trip, I > could have easily been stuck in Idaho for 6 or 8 weeks instead of the > 3.5 I was there. > > I just don't know if there is a good answer to this question. > Personally, I don't think that a cache should be allowed to be > archived just by a cacher making a comment to an admin. > > > > Scott > > wood@myblueheaven.com > www.myblueheaven.com