Should ruins or caves on public land be secrets?
Posted: Jan 31 2020 4:03 pm
When I started hiking I was surprised to find sharing some public locations was frowned upon. That's putting it lightly. Rather a virtual knock on the door by the concerned. More times than not I was told what I was allowed to do on public land.
My thinking was and is that scaring folks away is a stupid angle. It has created one ruins website I've crossed paths with that was specifically created out of hate for the lack of information. Let's just say it was created by Peter. Dare we even go into social media. Seems like proof that method backfired.
I've been near the initial sentence location in my hikes many times. It wasn't planned but I turned away as I approached. I'd rather be able to say with honesty, I've never laid eyes on it. Anyone that knows me, knows I avoid these locations. I just want to hike without controversy. There is plenty to see without ever going to ruins or caves. I created HAZ in hopes of a peaceful resource because someone was rude to me while researching information on a peak. If sharing historic places on public lands offends or is deemed irresponsible by a fair margin then I certainly do not want HAZ to fuel that fire.
When asked to delete geocodes on HAZ photos in sensitive areas I've gracefully complied. Same for aircraft wreckage, springs near private property, etc. There is a fauna label that if applied pops up "Location protected by HAZ Hikebot." I'm open to ideas to apply that tactic or such in other ways.
Since we have a fair sized group of like-welding jokesters it's monitored. Ultimately the moderated status on this topic too. Keep in mind there are other moderators for the forum. I do welcome those interested that show public signs of using that control while being impartial.
Perhaps no routes on ruins or dead-spot locations that allow nothing to be queried for a radius on such items. Perhaps no guides on ruins or caves period. Peter is praying he gets more traffic...
RS in beta has new labels for route finding, technical, no dogs. Point is, HAZ is the accumulation of ideas. It's member driven. If running away, posting garbage, supporting corporated driven instead and turning off HAZ is the answer let's hear it.
My thinking was and is that scaring folks away is a stupid angle. It has created one ruins website I've crossed paths with that was specifically created out of hate for the lack of information. Let's just say it was created by Peter. Dare we even go into social media. Seems like proof that method backfired.
I've been near the initial sentence location in my hikes many times. It wasn't planned but I turned away as I approached. I'd rather be able to say with honesty, I've never laid eyes on it. Anyone that knows me, knows I avoid these locations. I just want to hike without controversy. There is plenty to see without ever going to ruins or caves. I created HAZ in hopes of a peaceful resource because someone was rude to me while researching information on a peak. If sharing historic places on public lands offends or is deemed irresponsible by a fair margin then I certainly do not want HAZ to fuel that fire.
When asked to delete geocodes on HAZ photos in sensitive areas I've gracefully complied. Same for aircraft wreckage, springs near private property, etc. There is a fauna label that if applied pops up "Location protected by HAZ Hikebot." I'm open to ideas to apply that tactic or such in other ways.
Since we have a fair sized group of like-welding jokesters it's monitored. Ultimately the moderated status on this topic too. Keep in mind there are other moderators for the forum. I do welcome those interested that show public signs of using that control while being impartial.
Perhaps no routes on ruins or dead-spot locations that allow nothing to be queried for a radius on such items. Perhaps no guides on ruins or caves period. Peter is praying he gets more traffic...
RS in beta has new labels for route finding, technical, no dogs. Point is, HAZ is the accumulation of ideas. It's member driven. If running away, posting garbage, supporting corporated driven instead and turning off HAZ is the answer let's hear it.