+narcissa Posted May 27, 2016 Share Posted May 27, 2016 It is worth noting that one of the major complaints people have about challenge caches is that they were being used more and more as a way of excluding classes of finders from otherwise banal urban hides, rather than as a means of truly inspiring geocachers to do more. Placing a cache at the top of a mountain is a much different thing than putting a cache on a guardrail and adding an extreme set of ALRs. And if the challenge cache in question inspired you to find the cache at the top of the mountain? The actions needed to find either one are limiting by their very nature and similar in that regard. They both exclude classes of finders. However, if you're willing to do what's needed to log each one as found, you won't be excluded any more. I don't see exclusion as a huge issue unless exclusion is the actual purpose. And unfortunately, some cache owners really were placing challenges that were designed solely to exclude people. I think it's for the best that reviewers have some latitude here. But you brought up exclusion as one of the major complaints about challenge caches. I'd like to see an example of a challenge cache that was designed solely to exclude people. Was it really that rampant, especially since challenge caches were less than 1% of all submitted caches on the site? It was present enough that people were complaining about it during the feedback process, and it is something some challenge owners admitted to doing in the absence of other good ways to protect their caches from app users etc. I think the new rule is simply meant to give reviewers the latitude to address this if it looks like it is happening. It really looks like they have done their best to collate all of the feedback into a policy that is a fair compromise. Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.