[Az-Geocaching] New trend in geocaching? Must be easily findable?

[Geocaching 7/01]

If nothing else it discourages placement of a cache far from your home. OTOH, these present a challenge if the owner doesn't remove them. Wolfb8 placed a cache in NM some time ago that I would like to find--been disabled for years. Took us several tries to find Sparky's Cache--there were lots of DNF, but never disabled.
  ----- Original Message ----- 
  From: Gale 
  To: listserv at azgeocaching.com 
  Sent: Saturday, November 28, 2009 8:21 PM
  Subject: [Az-Geocaching] New trend in geocaching? Must be easily findable?


        A recent stink on the national forums was about a cache that had not been found in the two years of its existence despite many attempts. Cachers were concerned that it might happen again.

        It did. Here in Az. GC21D5M Folks were looking for this 2 day old cache and not finding it. Now its been disabled by the reviewer because it had too many DNFs, so the owner can check on it, despite the fact that the owner checked on it twice. Is this a new trend in geocaching? All caches must be easily findable by most people? 


        Tsegi Mike and Desert Viking

        Till a voice, as bad as Conscience, rang interminable changes
          On one everlasting Whisper day and night repeated -- so:
        "Something hidden.  Go and find it. Go and look behind the Ranges --
          "Something lost behind the Ranges. Lost and waiting for you. Go!"

        Rudyard Kipling ,   The Explorer  1898 




------------------------------------------------------------------------------


  ____________________________________________________________
  Az-Geocaching mailing list listserv at azgeocaching.com
  To edit your setting, subscribe or unsubscribe visit:
  http://listserv.azgeocaching.com/mailman/listinfo/az-geocaching

  Arizona's Geocaching Resource
  http://www.azgeocaching.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.azgeocaching.com/pipermail/az-geocaching/attachments/20091129/50406d64/attachment.htm>