The 3-caches limit for the regular members (people not paying the yearly Groundspeak fees) is insanely low, and there is nothing you can do about that.
However, it is not normal behavior to count the same cache twice if it's visited twice within the last 24 hours.
Viewing full description of cache X
15 minutes later, going back to view cache X counts it again! (and could be blocked if 3 caches have been seen in total)
Of course Groundspeak could implement that easily ("if cache X was part of the visited ones in the last 24h, don't count it again"), but that's unlikely (I've been a GC for many years, and it seems GS is becoming more and more money oriented).
Cachly could simply cache (the computer science term) the last full description of a number of caches, or the caches seen within the last 24 h.
Thus Cachly wouldn't have to do a request to the server when a description has already been downloaded recently.
Question
Langue de chat
Great appli, well programmed!
The 3-caches limit for the regular members (people not paying the yearly Groundspeak fees) is insanely low, and there is nothing you can do about that.
However, it is not normal behavior to count the same cache twice if it's visited twice within the last 24 hours.
Of course Groundspeak could implement that easily ("if cache X was part of the visited ones in the last 24h, don't count it again"), but that's unlikely (I've been a GC for many years, and it seems GS is becoming more and more money oriented).
Cachly could simply cache (the computer science term) the last full description of a number of caches, or the caches seen within the last 24 h.
Thus Cachly wouldn't have to do a request to the server when a description has already been downloaded recently.
Link to comment
Share on other sites
4 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.