I am currently developing an "online version" of the Reverse Geocache and I would like your input.
https://wiki.geocaching.com.au/wiki/Reverse_cache
You hide a geocache that is "locked" with something like a combination padlock. The geocache is at the published co-ordinates. You use the "geochecker" to list a 2nd set of co-ordinates (which are hidden) where your "code" to unlock the combination lock will be displayed to the seeker. This could be anywhere in a "reasonable" distance as they will need to come back and rehide the box.A Reverse cache is a type of geocache where a finder is guided to a specified location or target location. i.e. The box will help you to arrive at a specific location. At the location, either a log book is revealed to be signed (for example, a box can be opened) or a logging requirement (such as a description of the location or code) is made known to the finder.
Using a browser on their phone which uses their GPS on the phone they visit a page at GCA and are given a "distance" (but no direction) to the location you need to go to get the "unlock code". e.g. 2,456 metres.
They move a distance away and revisit the page and you get a different distance (but still no direction). e.g. 1,589 metres.
Depending on the accuracy of the GPS they now have two "circles" based on where they were and the distance the geocache was from each of the points. Where the two circles intersect the code will unlock at one of them.
They can move a 3rd time and check again and where all 3 circles intersect should be the location. e.g. 923 metres.
That depends on the GPS accuracy, and will never be perfect so as they approach the location they identify, they can check again and again and once they're within 10m of the location will show them the code to unlock the cache.
They unlock the cache, log it, and replace it back at the original co-ordinates.
You could also hide the box at the 2nd set of co-ordinates and then when the seeker gets within 10m of the location, they are given the final co-ordinates which is where the geocache cache is hidden AND the code to unlock it. This means no returning to the original location to rehide the box.
You could also give a third set of co-ordinates. The first set indicates the "area" (like a mystery cache). The 2nd (hidden) provides the distance to get the unlock code. The 3rd would be the geocache which could be nearby and you can only get those co-ordinates when you get the unlock code.
Seems a little convoluted I know, but this gives a way to hide a reverse geocache with a similar experience to a true reverse geocache in getting to an area "unlocks" the geocache BUT you don't have to make the box with all of the technical wizardry inside it. Just a box with a lock and some co-ordinates to get the code.
To minimise brute force the seeker would only get "10 tries per day". i.e. No just running around playing "hotter or colder". They would need a strategy. The seeker would also be restricted to 1 try every 2-5 minutes. i.e. They need to move and wait before trying again meaning a strategy is required as they hone in and less "hotter or colder" just moving around.
That's the pitch and the reasoning behind the details.
I would like input as to whether you think this works, whether this "trivialises" reverse geocaches and whether the restrictions are too tight or loose as well as the ideas on how to hide the cache and get the code without being too painful to have to return the geocache too far away.
I can't guarantee all or any of the suggestions are adopted but a conversation means we can, as a group, help to refine how we can try to increase the numbers of these geocaches.