I am a cache owner of a couple of challenge caches1. When you are a cache owner of challenge caches there are two possible tactics when dealing with people logging your caches:
- Manually check and enforce that people logging the cache as found actually qualify to do so AND have adequately documented that they qualify to do so in their log.
- Don't give a damn. Let whoever log whatever.
Anything in between will be unfair to those who actually does sit down and reads the logging requirements and follow them.
What I am proposing is that since there is a challenge checker system aimed at challenge cache owners that will monitor whether those who log challenge caches as found actually qualify and has documented this as is specified in the cache description. The service would identify violating logs and notify the cache owner who can then take action on bad logs.
As far as I can tell, Project GC already monitors new logs submitted and tries to monitor log edits. It should thus have the "toolbox" available to implement such a feature. I wouldn't mind it being a paying members only feature that you would have to activate first.
A good case study of this would be https://coord.info/GC48QDA .
I know that that particular kind of challenge cache has been grandfathered now but it illustrates my point. Many people has not read the ALR properly and being a cache owner on such caches can be tedious work. I would write the scripts to do so myself but I lack the API access to do so.
Any thoughts on this? I know that it is a narrow use case in terms of audience but useful none the less :)
1) There is a list here: https://coord.info/BM2MKFM