search

steve8x8 / geotoad

Geocaching query tool written in Ruby
https://buymeacoffee.com/steve8x8
Other
28 stars 8 forks source link

Poll: How to handle caches which become Premium-Member Only during their lifetime? #302

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently, for Basic Members, GeoToad ignores PMO caches.
If a cache was "public" in the past, and has been declared "PMO" afterwards, 
GeoToad will overwrite the cache description file, and therefore make the cache 
unfindable.
This would not happen if you kept a paper copy of the cache description - 
should GeoToad have the opportunity to at least present the latest known state, 
instead of completely ignoring the cache?

I'd like to learn your opinions.

Original issue reported on code.google.com by Steve8x8 on 30 Apr 2014 at 10:33

GoogleCodeExporter commented 9 years ago 
Same oppinion like on twitter...keep it.  ;-)

Original comment by GC.Womba...@gmail.com on 2 May 2014 at 8:15

GoogleCodeExporter commented 9 years ago 
I'm still a bit shy because I have seen PMO cache owners go nuts when a Basic 
Member dared to find a PMO - but the reviewer decided as I expected: only the 
physical log counts, no matter how you found the container.
As it's not forbidden to keep old printouts, keeping cdpf files must be allowed 
in the same way.

Getting PMO coordinates or waypoints is a different story though - well, you 
could still ask someone who has access to the information, be in the same team, 
or even married to her...

Here's the current patch set, working against r1609 but should cause no 
problems with any post-3.20 version

Original comment by Steve8x8 on 2 May 2014 at 8:35

Attachments:

GoogleCodeExporter commented 9 years ago 
There's one caveat which should be noted: As long as there are no coordinates 
read from the actual cache description page, the resulting position (taken from 
the old, non-PMO version of the page) may be wrong - like the whole cache 
description.
As an estimate from my region, about 1/5 of all caches converted to PMO will 
also be relocated, and I can't tell about the changes in descriptions / 
multi-cache tasks, for obvious reasons ;)
So I guess you have to live with it, it's a penalty for being late (not finding 
the cache while it was still "open").

Although the patch has been merged into trunk, I'll leave this issue open for 
further discussion.

Original comment by Steve8x8 on 18 Jun 2014 at 11:24

GoogleCodeExporter commented 9 years ago 
Anyone?

Original comment by Steve8x8 on 20 Aug 2014 at 6:59

GoogleCodeExporter commented 9 years ago 
Some code to cover this issue has been rolled into the latest release. I'd love 
to get feedback.

Original comment by Steve8x8 on 11 Sep 2014 at 2:40

GoogleCodeExporter commented 9 years ago 
No feedback means no problems? Fine...

Original comment by Steve8x8 on 17 Oct 2014 at 12:45