+brendan714 Posted May 26, 2017 Share Posted May 26, 2017 I guess the big question is, why is the page locking necessary? Wouldn't just archiving be enough? Sure, archiving would be "enough" if one can count on geocachers to only log archived listings legitimately (like being behind on logging finds, or when splitting up a team account into individual accounts). Is that a safe assumption to make? As my response, every non-legitimate log on a virtual or webcam cache post-archival is hereby incorporated by reference into this post. The archived Project APE caches are locked for similar reasons. If that's your argument, then why aren't ALL caches locked after being archived? Simple. There are valid finds on archived caches. For example: https://coord.info/GLMP0CFY ...(I found that cache more than a year after it was archived). Exactly my point. So why lock the brass cap & YOSM pages when there is potential for legitimate finds? The potential for illegitimate found logs is not a good argument for locking a cache page. So why were they archived AND locked? Read the rest of my post: Since the brass caps/YOSM are essentially virtual caches, the excuse would always be that "the monuments are still there, so I should still be able to log them". And what's the issue with that? It's no different than an archived cache that's in place. It's still there, so you should be able to log it! 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.