Jump to content

me N u

+Premium Members
  • Posts

    343
  • Joined

  • Last visited

Posts posted by me N u

  1. The needs maintenance nag does show when you attempt to publish a new cache. Of course you won't see that if you aren't into hiding caches. I agree that it couldn't hurt to have placed more prominently.

    Especially if it also noted how to log an Owner Maintenance log once you have checked on the cache so we can stop seeing those lingering NM attributes after an owner has actually performed maintenance! :anicute:

     

    If there's a list of your caches that need maintenance on your profile there's no reason why each cache shouldn't have a link to write a log when the maintenance has been done, to make sure the log is an Owner Maintenance type rather than a Note type. Maybe it could have three links - one to acknowledge the maintenance issue and indicate when it might be addressed, another to disable the cache if the owner can't get to it for a while, and a third to log Owner Maintenance to show they've dealt with it.

    Also, takes the onus off of the Reviewers. Many try to help the game by "sweeping" their jurisdiction 1-2 times a year. This way the cache ownership and maintenance responsibility from the guidelines (that pesky box every cache placer checks...) falls back right to the owner where it belongs.

     

    I wouldn't mind a nag to get after a NM log. Wouldn't bother me one bit.

     

    But, as more and more people cache solely from the Apps, I would hope the website interface finds itself more in line with what you see in the app

     

    It would make the reviewer's job somewhat easier in that any cache that had the NM flag for more than some designated period (say six months) could just be archived without having to ask what, if anything, the owner planned to do with the cache. If they haven't seen the reminder for six months they're inactive, end of.

     

    There must be some way the site could run a periodic process to find caches disabled for, say, six months or more and produce a report that reviewers could use. It could also find caches with longstanding NM logs that haven't been addressed.

     

    Problem with this is that many COs will not use the "Owner Maintenance" log, instead writing a Note or Enabling it after it has been disabled. There are countless active caches out there that have old NM logs still attached to them that the COs never cleared out properly.

     

    I suppose if the nag in the OP were implemented, it would also show a link explaining to the CO how to clear out the NM 'red wrench' and get it off the nag screen...but this is all assuming the CO is still active and uses the website and views their profile page. That's a big assumption...

     

    If the CO is inactive the cache needs to be archived.

     

    If the website and all the various flavours of app have very visible notifications when your owned caches need maintenance then it's perfectly reasonable to archive anything that has had an NM flag on it without a response from the owner in a couple of months.

     

    The point is to make it very visible when your caches need maintenance and very clear how to perform and log maintenance to get them off the list. If very visible notifications are implemented and people still fail to maintain their caches, the reviewer can archive them.

     

    The larger concern is the cachers who do things like log Owner Maintenance with text that says "Got some more of these on order, will replace it next week".

     

    Or even in 3 months time, by which time the cache will have been disabled for 6 months -

     

    "Probably won't get home til Christmas now so will sort out all the geocaches in the series then" (sic)

  2. A fairly recently published "night cache" was found in daylight by a local cacher who used local knowledge and a hunch to go straight to the final location and claim FTF, cue sour grapes and a strongly worded whinge in the form of a write note on the cache page (since deleted) from others who then claimed "FTF in the dark"

  3. :) Found it

     

    24/07/2014

     

    Claiming half a find for this - found and solved puzzle - put co-ords into GPS only for batteries to fail. No problem insert back-up batteries ......also flat

     

    Moral of the story - always check your equipment and spares before setting off

  4. Shame the excellent idea from The Blorenges from almost 3 years ago to remove ghost trackables has been ignored even though it was "submitted"

     

    Sorry unable to work out how to do a link to the topic in question, but its in the website forum.

  5. Member #3 04/10/14

    783 finds

     

    Needs maintenance

     

    There may now be 2 containers here following a recent throwdown - maybe the owner could check on the original?

     

    Throwdown cacher 29/09/14

    8508 finds

     

    Found it

     

    Had a good look for this one without success. Noticed CO has not been on this site for over 2 years so left a replacement 35mm and new log in the tree under a white stone to keep this one going. SL TFTC

     

    Member #5 14/09/14

    156 finds

     

    Did not find

     

    The cache is missing

     

    Member #4 6/09/14

    332 finds

     

    Did not find

     

    Found GZ, followed the hint, but came up with nothing. Will try again, if it's still there!

     

    Member #3 24/05/14

    783 finds

     

    Did not find

     

    Came on foot from Gwennap via public footpaths across fields, had a good rummage around but failed to find the cache.

     

    Our GPS indicated GZ as in the field rather than on the path, but we found items matching the hint by an oak tree on the lane.

     

    Member #2 04/01/2014

    42 finds

     

    Found it

     

    That’s one more find for me! Thanks so much for hiding this geocache.

     

    Member #1 23/11/2013

    1998 finds

     

    Found it

     

    A dash out on a blurry saturday, in the middle pof moving house, for a calendar tile. TFTC.

  6. Additionally, after the cache adoption request has been sent, you get an automated email. My email said "Your Trackable adoption request has been sent" yet it was not a trackable, but a traditional geocache.

     

    The same happened to us just a couple of days ago, we were going to put it on here but no point in double posting.

  7. We've found a cache by accident twice.

     

    The first was GC6PN5 a multi cache, we stopped for lunch and sheltered out of the wind, Mrs me N u thought this would be a good spot, looked in the hole she was next to and there was a cache container, we signed the log then went on to find the clues.

     

    The second was GC2D65V a micro that we had deselected from the PQ for the walk, stopped for photos and noticed the container.

  8. According to QI, the first words were part of commentary Buzz Aldrin gave as he brought the LEM in to land. Those first words were "Contact light". "Houston, this is Tranquility. The Eagle has landed." (or something similar) was uttered a short while after.

     

    We're afraid this is the closest to what we were after - radio protocol is to say who you are calling, followed by your callsign then the message.

     

    So it would be a DING, except nobody can hear a ding in space!

     

    Over to you Pajaholic

     

    Edited for spelling.

  9. A couple of Tbs we have helped on their way went way off course later on.

     

    One was trying to get from the Netherlands to Australia, we dropped it off in Singapore, it was retrieved and dropped off in a cache in Germany!

     

    Another was trying to get back to Finland, it made it as far as Sweden then was dropped off in New Zealand.

     

    Must be really frustrating for the owners.

×
×
  • Create New...