Trez

You are right. I was getting frustrated and reacting a bit immaturely with the tone of the listing. Thanks for the input in how to appropriately list it. I've taken your suggestion and used your wording above. (I hope you don't mind.) I sincerely appreciate the assistance. Lisa

Some people just can't seem to let it go... now the son comes in with: To which I made no reply. I started to tell him that he didn't owe any apology, as he had done nothing but post his opinion, he had not threatened or harrassed me, it was his father (On this guys profile page it shows that "Handycapt", the one who WAS harrassing me, is his father) who owed an apology, but decided to just let it go. but then this morning I get this: I took someone else's advice and just deleted the log entry. Are there just people out there that really have no life and must find ways to harrass those of us that do? Anyone out there want to adopt this cache? I do not have time for this kind of headache.

By the way, I just found out that the original wording of the cache listing where they (my exhusband and my kids who listed this cache) said "A cache that requires some up hill walking and climbing." was a *tongue in cheek* comment .... you see there are a set of man made STEPS to *climb* up. There's definately no climbing gear needed for this cache. Thought those of you who have been following this all along might find that amusing, I sure did, considering all the hoopla that one gentleman has made about this cache.

Talked with the Sherriff's department (for the County where the cache is, the ones who left a note in the cache to contact them last year). They have no problem with the cache and encouraged me to contact my local sherriff's department with the content of the emails from Handycapt. Also spoke on the phone today with a gentleman from Groundspeak. I'll be updating the information on the cache tonight. Thanks so much, Lisa

Has anyone noticed that this man has now removed not only his posts (there were two) from the cache page, but removed his picture from his profile, and came back to this forum and basically removed his diatribe from this page as well? I am now starting to get the creeps from this, and all I was trying to do from the beginning was let him know that I saw his complaint and someone would check it out. things grow stranger by the moment.....

Just got in tonight after being gone all day. The posts from Handycapt have been removed from the cache page, we didn't remove them. Does that mean he's gone in and retracted his posts? I recieved another email from him: ??? okie. G'night folks. Thanks for all the information. Lisa

So the kids went out to check on the GeoCache yesterday. It is still chained to the same bush, but it had been moved around towards the drop off side. They moved it back to the trail side. Even so, the drop was a good 10 feet away from where the cache is, and the drop is approximately 15 feet, not 30 or 40 as the complainer indicated. The cache IS ON A VISIBLE WORN TRAIL, hidden only by the pine straw and leaves from sight, and the log indicates that it has been frequently found by accident (not Geocachers looking for it.) It really isn't as if it's way off the trail hanging over a precipice as the gentleman Handycapt implied in his post on the cache page and in his emails to me. They did find the note from the Clay County Sherriff's Department, it simply said "Please notify Clay Co. Sherriff Office next time you do this." It was dated 2-10-2007 and indicated that they left it at 1:00 p.m. The kids put a new log book in and added some stuff to the cache, should one of them post on the cache page? By the way, the very interesting thing was that there were NO entries in the logbook from August... the last log was in July 2008. The log book does show several repeat visits from at least three different GeoCachers. One last note... my 19 year old daughter twisted her ankle Friday (unrelated to the cache at all) and had to go have it x-rayed to make sure she hadn't fractured anything.. .pretty tough sprain... she STILL made it to this cache Saturday morning to check on it. I can't imagine it being THAT tough or dangerous to get to if she could make it to the cach hobbling with a wrapped ankle. Thanks to all for the input...

I emailed the gentleman a link to this conversation. Thanks to everyone for the input. My son and daughter (both now grown) are going to get together this weekend and go check on the cache. This will probably be the first time they have been hiking together in about 5 years. :-) Something good coming of some idiot ranting and raving, eh? Thanks again, Lisa

I think that's the best idea I've heard all day. Thanks, Lisa

I'm assuming this is the right number, it's from the upper left hand of the page of the log: GC7366 Highfalls, AL Trez is my son's username. youguys reply too fast for me to keep up!

I sent a message to the gentleman this morning: Hello, In regards to the cache at High Falls, this cache was created in 2002 by my x-husband and my two children. 88 people have visited the cache and for the most part the overwhelming majority have found it to be a good cache. My x-husband lives in another state and my son has moved away. My daughter said she will go double check in the next week or so and see if somehow it has become closer to the cliff than originally set up. (Erosion, growth of the bush, etc.), however, in 88 finds, no one else has ever felt so strongly that this cache was "dangerous", but we will "do the right thing" and check it out. And IF it really has become dangerous, will 'archive' it. Thank you, Lisa Durham And his response was: Regardless the number of people that said it was fun, the cache is unsafe. It hangs over the edge of a 40+ foot sheer drop to rocks below and the footing is covered in pine straw near the edge. The number of anonymous and unverifiable claims of fun will hold little to no weight against a jury's decision. If anyone is injured or killed because of this cache I will use this correspondence during litigation. One of the members of our caching party is an attorney, and in his opinion, the cache placement constitutes a needless and careless risk to people lives. We took extensive photos to document the placement (which you confirm that your team intentionally placed close to the cliff). What do you think is going to happen when someone is injured or killed due to the placement of a device you invite people to come get? Your team is responsible for this cache. Do you really want that type of downside risk? Why did you place it near the edge at all? There are plenty of safer hiding places near the falls. Had someone been hurt before this, you might have claimed that it was unintentional, but now there is no basis for such a defense claim. Do whatever you wish with the cache, but for our part we will side with any party injured/killed at this cache. ===================================== end quote I'm not very familiar with GeoCaching, but I thought we were responding appropriately, should we be doing something differently? I'm not sure what this gentleman's issue is. I'm going to call my son and ask if he's ok with me allowing someone else to take over this cache. I know the place where it's located and it's a beautiful setting. Like I said, I get occassional emails from people and most are positive. I can't imagine why this man has decided to be so confrontational with me. If someone wants to 'adopt or take over' this cache, please let me know. Thank you, L. Durham

My son created this Geocache account many years ago and he and his father created at least one Cache. He is grown now and no longer lives at home, he no longer uses this email address or is involved in geocaching. Anyway, I occassionally get messages that someone has found the cache, and it brings a pleasant smile to my face to remember my son and his father hiking in the woods. Now, suddenly someone who JUST JOINED Geocache about a month ago has repeatedly posted that this cache is DANGEROUS (in 6 years with 88 finds, I think this is the FIRST time someone has called it "Dangerous".) and is asking that the cache be "Archived". . Why would it suddenly be considered dangerous after over 6 years and almost 100 people finding it, and if it really is dangerous, how would I go about 'Archiving' it? Thank you, Lisa Durham