Attached is an e-mail I received this evening from Geocaching Reviewers.
This is the background to the situation. Ever since I started caching back in late April, I had attempted to find a certain cache in Wells, Maine GCVCNF Wells Rec/Hobbs Pond Cache. It was listed as a Traditional cache, and every time I tried to find it, I came up empty handed. The cache cords LISTED were in fact no the cords of the cache but cords of a "clue" that you were to find which would lead you to the actual cache location. As we all know, this is not a Traditional Cache. This should be a mystery cache, or even a multi-stage if you were looking for a first set of cords. But the listing really was vague about what you were to look for. Heck, in the listing, the cache owner even says that the listed cords are off by quite a bit!
I went back several times over the summer and each time I was unable to locate it. Finally, Marcipanek and Fjordriders both found the cache and explained to me how to find it. I finally went back in November and located the cache. But in the meantime during the time I couldn't find it, I had e-mailed the cache owner several times regarding the cache, without getting any kind of response. I finally explained that the cache was not a traditional cache, and it should be corrected so as not to confuse cachers. I knew from dicussions with other cachers, even on site who I had run into, that this was becoming a problem as they were having problems with the cache as well. I told the cache owner that if I did not hear anything back this final time, I would be contacting MainePublisher regarding the cache and how it was improperly categorized and that it should be archived and fixed. Still, I received no response from this cache owner.
So, when I finally did find the cache with the help of Marcipanek and Fjordriders, I decided to place a cache in the vicinity (but over .1 miles away from both the listed cords and the actual cache location) called A TRUE TRADITIONAL CACHE. When I placed it, suddenly, GCVCNF was archived by the cache owner. In her archive log, she stated that she would be reactivating cache as a mystery cache. This was in Novemeber. At the same time, MainePublisher also temporarily disabled my cache without publishing it saying that there was a proximity issue with an exisiting cache in the area and that I had to wait for the proximity issues to be resolved. So, to simplify here, her cache was archived and mine disabled without publishing, leaving no caches on the trail system what so ever. So I wait and wait and wait. I emailed the Keds (the cache owner) wondering when she would be activating her replacement cache. Still no response. I emailed MainePublisher after several weeks about it and was told that I had to wait until Keds activated her cache, so he could review my cache in relation to her cache (which still isn't there). So, finally this weekend I emailed Groundspeak and MainePublisher about this. It has been almost three months without Keds activating her replacement cache.
And this is the response I got from Groundspeak. Frankly, I am insulted! I am told that my cache will not be published because it is in close proximity to this woman's cache which she hasn't even activated or gotten published? She has had almost three months to activate it. MainePublisher has had almost three months to tell me that he won't be publishing my cache. And then I am told not to email Keds about this anymore? She refused to respond to ANY of my messages months and months ago concerning this issue!
It seems that whenever ANY issue arises with any of my caches, TAT pulls the plug on them IMMEDIATELY and they get archived, yet when there are issues with other's caches, it takes months t get them archived. I have seen caches get 20 DNF logs on them and many "Needs Archiving" logs and still no action by MainePublisher. Yet, mine get nailed at the first possibility of an issue.
I placed a cache several weeks ago at the trailhead of a nature preserve in Saco, Maine. Petr (Marcianek) placed a cache .25 miles down the trail in the middle of this preserve two weeks before and it was published (heck I snowshoed to FTF on it!) yet MainePublisher refuses to publish my cache saying that it is located on the property of a nature preserve that does not allow Geocaching on it's property. Yet, Marcianek's cache (3,2,1,Go!) get's published without an issue on the SAME damned preserve! Something is not right here.
Heck, look at THIS cache GCJ9AD (Cliff Cache). Marcipanek brought this one to my attention. This stuff is really allowed to continue as a cache?
I am just so frustrated with these double standards regarding cache placements. It seems everytime I go caching, I come across caches which are VERY close to rail road tracks as well. Over the summer as some of you know, I had an issue with a cache I was placing in Thomaston, Maine that was under the 150 ft minimum of distance to railroad tracks (regardless of how the cache is placed). Yet, I come across caches that were reviewed by MainePublisher AFTER the problem over the summer regarding my cache and rail road proximity, all the time. Do I make a stink about them? No. Mainly I don't because most have been placed by my friends. But regardless, he will publish those caches without problem but gives my caches the most scrutiny. I realize, yes MainePublisher is a volunteer. Yes he has published A LOT of my caches recently without problem, or complaint. I am very appreciative to him for his efforts. However, it does not excuse this type of double standard and the treatment of my cache in Wells. And to receive this type of email from Groundspeak, I feel personally insulted and singled out.
What are your opinions?
Begin forwarded message:
From: Geocaching Reviewers <firstname.lastname@example.org>
Date: February 1, 2010 6:34:46 PM EST
Subject: [REV #LTM-609764]: GC20YWA
I have heard back from the local Maine Reviewer, and have an update about the cache in question. As you will remember from your correspondence with us last year, you pointed out that GCVCNF functioned more like a multi-cache than a traditional cache. Subsequently the cache owner, keds, has put in place the stages of their multi and this cache will be published very soon (with a new GC code).
Your cache, if it is still in the location it was when you began writing to us, will have a proximity issue with the cache above. For your cache to be published, it will need to be moved. My best advice is to keep an eye on new caches in coming days so you can best place your cache away from any other waypoints.
Also, I would recommend changing the name of the cache before you submit is again, as it not really in keeping with the good-natured spirit of geocaching.
Lastly, I have subsequently discovered that you used geocaching.com to contact the cache owner keds, and that the content of these emails was less than friendly. Please do not contact this cache owner, as we cannot condone the use of our site as a medium for this type of behavior.
I understand that after a long wait this will not be the news you had hoped for. I do hope that you will be able to come up with an innovative alternative location that meets our guidelines so that we can publish your cache page soon.
Groundspeak - The Language of Location
Ticket ID: LTM-609764
Department: Cache Appeals