From az-geocaching-bounces@listserv.azgeocaching.com Tue Dec 1 02:57:17 2009 Return-Path: X-Original-To: geolurker@listserv.azgeocaching.com Delivered-To: geolurker@listserv.azgeocaching.com Received: from cornwallis.duncanmultimedia.com (localhost [127.0.0.1]) by duncanmultimedia.com (Postfix) with ESMTP id 605216C4004; Tue, 1 Dec 2009 02:57:17 -0600 (CST) X-Original-To: listserv@azgeocaching.com Delivered-To: az-geocaching@listserv.azgeocaching.com Received: from imr-da01.mx.aol.com (imr-da01.mx.aol.com [205.188.105.143]) by duncanmultimedia.com (Postfix) with ESMTP id 84E76B8020 for ; Tue, 1 Dec 2009 02:57:15 -0600 (CST) Received: from imo-ma02.mx.aol.com (imo-ma02.mx.aol.com [64.12.78.137]) by imr-da01.mx.aol.com (8.14.1/8.14.1) with ESMTP id nB18v5b2024294 for ; Tue, 1 Dec 2009 03:57:05 -0500 Received: from PTPENNY@aol.com by imo-ma02.mx.aol.com (mail_out_v42.5.) id b.beb.54e01d7e (44620) for ; Tue, 1 Dec 2009 03:57:00 -0500 (EST) Received: from smtprly-dd03.mx.aol.com (smtprly-dd03.mx.aol.com [205.188.84.131]) by cia-mc01.mx.aol.com (v126.13) with ESMTP id MAILCIAMC011-d40b4b14da591b8; Tue, 01 Dec 2009 03:57:00 -0500 Received: from webmail-m017 (webmail-m017.sim.aol.com [64.12.101.101]) by smtprly-dd03.mx.aol.com (v126.13) with ESMTP id MAILSMTPRLYDD037-d40b4b14da591b8; Tue, 01 Dec 2009 03:56:57 -0500 References: <443227.42064.qm@web54207.mail.re2.yahoo.com> <4B13C6F1.1050607@gmail.com> To: listserv@azgeocaching.com Date: Tue, 01 Dec 2009 03:56:57 -0500 X-AOL-IP: 12.110.39.162 In-Reply-To: <4B13C6F1.1050607@gmail.com> X-MB-Message-Source: WebUI MIME-Version: 1.0 From: ptpenny@aol.com X-MB-Message-Type: User X-Mailer: AOL Webmail 29202-STANDARD Received: from 12.110.39.162 by webmail-m017.sysops.aol.com (64.12.101.101) with HTTP (WebMailUI); Tue, 01 Dec 2009 03:56:57 -0500 Message-Id: <8CC407B5F0D7B59-279C-960F@webmail-m017.sysops.aol.com> X-Spam-Flag: NO X-AOL-SENDER: PTPENNY@aol.com Subject: Re: [Az-Geocaching] New trend in geocaching? Must be easily findable? X-BeenThere: az-geocaching@listserv.azgeocaching.com X-Mailman-Version: 2.1.10 Precedence: list Reply-To: listserv@azgeocaching.com List-Id: List for discussing Geocaching in Arizona List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5623737479271251924==" Mime-version: 1.0 Sender: az-geocaching-bounces@listserv.azgeocaching.com Errors-To: az-geocaching-bounces@listserv.azgeocaching.com --===============5623737479271251924== Content-Type: multipart/alternative; boundary="--------MB_8CC407B5F822041_279C_130F9_webmail-m017.sysops.aol.com" ----------MB_8CC407B5F822041_279C_130F9_webmail-m017.sysops.aol.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" I am writing this note because this topic popped up in my e-mail. I don't= remember how to get into the AZ forums. I my experience, cache owners oft= en go back to check on a cache and don't use the coordinates that they hav= e posted. They go to the spot where they have hidden the cache, verify the= fact that is where they left it and post a note that suggests all is well= . Yep, the cache is where they left it but the coords might still be a pro= blem. I think that a reviewer's responsiblity is to facilitate the game an= d that is broadly interpreted.=20 -----Original Message----- From: AZcachemeister To: listserv@azgeocaching.com Sent: Mon, Nov 30, 2009 6:21 am Subject: Re: [Az-Geocaching] New trend in geocaching? Must be easily finda= ble? Thanks for pointing this out, so I can add that cache to THAT list. :-X= =20 AZcachemeister Gale wrote:=20 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 we= re concerned that it might happen again. It did. Here in Az. GC21D5M Folks were looking for this 2 day old cache an= d 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?=20 Tsegi Mike and Desert Viking =20 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!" =20 Rudyard Kipling , The Explorer 1898 ___________________________________________________________ z-Geocaching mailing list listserv@azgeocaching.com o edit your setting, subscribe or unsubscribe visit: ttp://listserv.azgeocaching.com/mailman/listinfo/az-geocaching Arizona's Geocaching Resource ttp://www.azgeocaching.com =20 ____________________________________________________________ z-Geocaching mailing list listserv@azgeocaching.com o edit your setting, subscribe or unsubscribe visit: ttp://listserv.azgeocaching.com/mailman/listinfo/az-geocaching Arizona's Geocaching Resource ttp://www.azgeocaching.com ----------MB_8CC407B5F822041_279C_130F9_webmail-m017.sysops.aol.com Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" I am writing this note bec= ause this topic popped up in my e-mail. I don't remember how to get into= the AZ forums. I my experience, cache owners often go back to check on a= cache and don't use the coordinates that they have posted. They go to the= spot where they have hidden the cache, verify the fact that is where they= left it and post a note that suggests all is well. Yep, the cache is wher= e they left it but the coords might still be a problem. I think that a rev= iewer's responsiblity is to facilitate the game and that is broadly interp= reted.


-----Orig= inal Message-----
From: AZcachemeister <azcachemeister@gmail.com>
To: listserv@azgeocaching.com
Sent: Mon, Nov 30, 2009 6:21 am
Subject: Re: [Az-Geocaching] New trend in geocaching? Must be easily finda= ble?

Thanks for poi= nting this out, so I can add that cache to THAT list.  :-X

AZcachemeister


Gale wrote:=20
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 cac= he and not finding it. Now its been disabled by the reviewer because it ha= d 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 interm= inable changes
  On one everlasting Whisper day and night repeated -- so:
"Something hidden.  Go and find it. Go and look behind the Ranges --<= br>   "Something lost behind the Ranges. Lost and waiting for you. Go!"
 
Rudyard Kipling ,   The Explorer=   1898


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

Arizona's Geocaching Resource
http://www.azgeocaching.com
  
___=
_________________________________________________________
Az-Geocaching mailing list li=
stserv@azgeocaching.com
To edit your setting, subscribe or unsubscribe visit:
http://listserv.azgeocaching.com/mailman/listinfo/az-geo=
caching

Arizona's Geocaching Resource
http://www.azgeoc=
aching.com
----------MB_8CC407B5F822041_279C_130F9_webmail-m017.sysops.aol.com-- --===============5623737479271251924== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ____________________________________________________________ Az-Geocaching mailing list listserv@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 --===============5623737479271251924==--