Jump to content

Delta68

+Premium Members
  • Posts

    1696
  • Joined

  • Last visited

Posts posted by Delta68

  1. As it stands no signature for a cache with a physical placement and you have no legitimate claim to the find. :o

    With a little bit of resolve most can still be signed, just try harder. :rolleyes:

     

    Yup! One of my colleges doesn't bother to sign logbooks.

    In fact, most of the time he doesn't even bother to open the cache. :o

     

    This is not a problem though because he doesn't log finds on-line either! :)

     

    For him, Geocaching is just something he does when he's on holiday and the fact that a cache has been paced somewhere gives him a reason to go there for a walk B)

     

     

    Mark

  2. I'd advise doing the physical caches as well or you might end up regretting it (take some TBs to drop off as well ;) )

     

    I have nothing against Virtuals but there's nothing quite like opening a cache at the end of a tough walk, signing the logbook and seeing the names of all those who have done the same.

     

    The physical Snowdon cache can be tricky because it's right in the Muggle zone

    Scafell Pike is pretty easy as it's a short way off the track

    Ben Nevis is one of my favourite caches ever! It's such a surreal place... B)

     

     

    Mark

  3. A process like this maybe?

    • CO starts new listing
    • CO checks the checkbox saying it's active
    • Reviewer reviews the cache page
    • Reviewer adds listing to a publishing queue which locks it
    • At scheduled time/date cache gets unlocked and published
      If desired publish date/time has already passed or no preference is specified, listing gets published immediately

     

    This would be great for scheduling new caches to be published at Events ete or for a large series to be published in bulk

     

    Mark

  4. We found a cache a couple of weeks ago which is listed as Trad but you need information from other caches in the series in order to unlock a combination lock.

    Luckily we did the series in the intended order and picked up the info on the way.

    Amazingly, even cachers who had to go back for it don't appear to have complained.

     

    Did I notify the reviewer?

    No. Can't be bothered.

    When they say it's up to us to help improve standards they don't really mean it :(

     

     

    Mark

  5. The reviewers have already looked at that cache and consider themselves satisfied, I'm more interested in a general debate about the issues surrounding this :)

     

    I'd say the reviewer is wrong.

     

    If it was just a case of needing spanner or screwdriver etc to open the cache then yes, it would still be OK as Trad.

     

    Having to go to another location first means it blatantly isn't a Traditional

     

     

    Mark

  6. I've done a few night caches and all except one* have just been 'follow the trail of reflectors' type of thing - no GPS required so it's not 'proper' Geocaching at all really! :rolleyes:

     

     

    *the odd one out was follow a trail to a micro containing co-ords for final location

     

    Mark

  7. This is not technically a bug, and so I'm moving it from the bug reports forum. The app has behaved like this for as long as I can remember, but I have a story in to change this behavior.

     

    WELL THAT WAS A WASTE OF TIME WASN'T IT ????102.gif

     

    It was already listed as a suggestion

     

    Have a look back at the uservoice forum. It was definitely changed to list the tracking codes instead of the 'TB' code not long after the ability to drop trackables was added to the iPhone app

    As this is no longer how it works, I would say it is a BUG

     

    Mark

  8. We very rarely use the iPhone app so didn't notice that this feature/bug had reappeared.

    When dropping a trackable in a cache, having the 'TB' code is no use whatsoever.

     

    It was reported and fixed in the days of the UserVoice forum so there's no trace of the original thread any more (not to us mere mortals anyway ;) )

     

    This need to be fixed to as soon as possible to prevent the wrong trackables being logged into caches

×
×
  • Create New...