Comments on: How to Avoid Geocache Saturation Geocaching Can be Addictive Mon, 25 May 2015 14:52:06 +0000 hourly 1 By: teamvoyagr Fri, 03 Dec 2010 20:00:53 +0000 Two ways to manage this.

  1. Return a yes/no response to the query. Would be hard to brute force an answer when all you know is it’s too close but not by how much.
  2. License access to the API to websites only. Apply restrictions to the number of API calls in a given period of time.

There may be no perfect solution. In the end we’ll need a better way to manage proximity issues. There is a finite amount of real-estate available to place caches. If we don’t manage this issue land managers are going to have a big reason to disallow any kind of caching.

By: northernpenguin Fri, 03 Dec 2010 18:39:36 +0000 One of the key issues with a proximity API is that people will utilize that to brute force puzzles. Take three sets of co-ordinates, and work them until you get a “denied” at 162M and voila, you know where the cache is.