TX Stephens
-
Posts
35 -
Joined
-
Last visited
Posts posted by TX Stephens
-
-
Bid placed for the Geo Honu turtle!
-
Received it yesterday! Thanks for the great coin and an easy transaction!
-
Ordered! Now we wait...
-
Bump!
Sending you an email!
-
Just a quick note... I placed the NA and our reviewer disabled it in minutes due to the string of DNF's. I am hopeful the at CO will replace it so others will go see the great area.
-
Gee whizz, I would have done a D5 on that one based strictly on the creepiness factor! Nice though!
-
Although you don't know for sure the cache is missing, it still needs to be checked because with a lot of failures and no successes lately, people are going to stop looking for it whether it's there or not.
If those people stop looking for it, that's their decision.
There might be reasons to check a cache, but that people might stop looking for it is not a legitimate reason for a cache check for me in its own right.
That's a bit like if you'd argue that someone who has a very difficult puzzle cache where the locals who can solve it have already visited the cache should be made easier or archiv it once the visits become very rare.
For whatever reason, I'm attracted to recent DNF caches as it is. I see them as a challenge I guess. I'm always fine with adding another one on if I am unable to locate.
Warning, you just stepped into the lion's den in this forum!
Yes, I can see how the comment could be read out of context. I meant I'm fine with having another DNF under my belt... not that I'm cool with adding a new cache in that location. That's wrong in my book. I updated that post to ensure I won't be eaten alive....
-
Although you don't know for sure the cache is missing, it still needs to be checked because with a lot of failures and no successes lately, people are going to stop looking for it whether it's there or not.
If those people stop looking for it, that's their decision.
There might be reasons to check a cache, but that people might stop looking for it is not a legitimate reason for a cache check for me in its own right.
That's a bit like if you'd argue that someone who has a very difficult puzzle cache where the locals who can solve it have already visited the cache should be made easier or archiv it once the visits become very rare.
For whatever reason, I'm attracted to recent DNF caches as it is. I see them as a challenge I guess. I'm always fine with adding another one on if I am unable to locate.
That would be a throw down - adding another cache when the original cache appears to be missing. People usually do this in order to claim a smiley and not a DNF. And usually when someone throws a cache container they too abandon it and never go back to maintain it when problems occur.
So THATS what a throw down is! SO sorry, I meant I'm always fine with logging a DNF when I can't find it. I would never just put a new cache down on someone else's territory. Thanks for the info, though!
-
I think this reply is without a doubt the most appropriate one in the thread. cheers!
-
I'd call it "Yankee Skirt Lifter". Australians may think the cache is risque, but Americans will know that it is anything but.
Only Yankees lift skirts?
To foreigners, a Yankee is an American.
To Americans, a Yankee is a Northerner.
To Northerners, a Yankee is an Easterner.
To Easterners, a Yankee is a New Englander.
To New Englanders, a Yankee is a Vermonter.
And in Vermont, a Yankee is somebody who eats pie for breakfast.
(attributed to E. B. White)
And to a Bostonian, a Yankee is a person who, well, to maintain a level of decency, wears a pin-striped uniform
Bahahhaha, that was a pretty great addition to something I thought couldn't get any funnier! Gold star for you.
-
Although you don't know for sure the cache is missing, it still needs to be checked because with a lot of failures and no successes lately, people are going to stop looking for it whether it's there or not.
If those people stop looking for it, that's their decision.
There might be reasons to check a cache, but that people might stop looking for it is not a legitimate reason for a cache check for me in its own right.
That's a bit like if you'd argue that someone who has a very difficult puzzle cache where the locals who can solve it have already visited the cache should be made easier or archiv it once the visits become very rare.
For whatever reason, I'm attracted to recent DNF caches as it is. I see them as a challenge I guess. I'm always fine with adding another DNF to my stats if I am unable to locate.
-
You're asking lots of good questions, questions many yearlings wouldn't think to ask, so I'm confident that you would have done something reasonable even without the good advice you've gotten from other responses. So I'm not going to answer so much as offer some sense of how I look at this issue.
The first question is, "If not me, who?" Some people don't have enough experience to take action, and that's fine, but I feel safe in saying that you know what you're doing here, so it's good that you're taking the bull by the horns. Some people -- and some areas -- think that it's the job of a reviewer to step in, but the idea is that geocaches are policed by seekers.
If enough DNFs have been filed to convince you it's missing, and you looked yourself and couldn't find it, then the cache needs maintenance, so you should file a Need Maintenance log. Although you don't know for sure the cache is missing, it still needs to be checked because with a lot of failures and no successes lately, people are going to stop looking for it whether it's there or not.
You're already on this path, so I wasn't so much telling you what to do as making sure you understand you've done the right thing. If nothing happens -- and it probably won't -- now it's time for a Needs Archived log.
I normally avoid logging an NA on a cache that I've logged the NM for. Instead, I let the system wait for a second opinion, someone else looking at the information and my NM and deciding independently that the jig's up. In my area, that always happens. Similarly, if I see an NM by someone else, I'll consider filing the NA. There's no particular time on this, but the 6 weeks number someone else mentioned is fine. For a second opinion situation, I'm comfortable after a couple weeks, if the case is obvious.
If no one else files the NA, though, it's OK to do it yourself. And then work on the local culture however you can to encourage more participation in the monitoring of your local caches.
All of this is independent of contacting the CO privately. Feel free to do that if you want. If he does come back to life, he sounds like a good person to know in your local community. And certainly write all your logs with awareness that they are also a form of personal communication even though they aren't private. But take action against the caches without considering the CO's status and whether you can get a reaction from him. Personally, I always imagine the CO is paying attention but is content to silently let nature takes its course.
I appreciate the input, dprovan. In fact, I appreciate the input of all. I think I am going to move forward with a NA. Hopefully that will help the situation move forward. (fingers crossed)
-
Long shot, but perhaps the CO is waiting for someone to leave a throwdown then they don't have to worry about anymore. I've seen this happen and it only confuses the situation particularly when another throwdown appears. Nip it in the bud early by leaving an NM, watch it for a month or so then NA. Especially as they are only D1.5.
Yes. Good point. I've seen plenty of abandoned caches with a few DNFs in a row and an owner that doesn't play anymore suddenly get "found" by a finder with the next finders having no problem locating it. Yet the CO never visited the site. The longer an abandoned cache festers the more likely someone will throwdown (they got to have that smiley). And usually the container is a leaky throw-away junk container that festers for months or years before someone finally posts an NM and then an NA. I agree, nip this practice in the bud.
Just so I understand, is a "throwdown" when someone logs a smiley when they actually didn't find the cache? If so, I could totally see how that would confuse the situation. Not to mention, it's just plain wrong. I could be mistaken of the meaning though...
-
I remember having 130 finds and being "certain" that a cache was gone. Hah!
Haha, that's why I wanted to put the information out front. Just so everyone knew where I was coming from.
-
I cooled off a bit, late last year after letting my streak lapse after 5 straight years. It was time consuming, a bit frustrating and the cost was ramping up as there were fewer caches along my usual drives.
Saved up my pennies and bought a Jeep.
Now I'm itching to get back into caching
Nice! I would love to have a Jeep as our caching vehicle! Enjoy!
-
I've been debating whether or not to post this, but I think it would be best to get some input from the experts. Let me preface this post with some facts:
I've been caching for just shy of a year;
I have about 130 finds;
I have not hidden any caches, though I want to.
Now that the formalities are out of the way, here is my issue:
Over the past few months, I have noticed that a number of caches from one owner have several DNF's for the most recent finds. I have not clicked through his or her caches to see how many do, but this person has a decent amount of hides in my area, so my cohort and I are naturally trying to tackle some. Let me provide you with two specific examples:
In April, we attempted to find a 1.5/1.5 regular sized cache in a local park. I visited twice (once with my better half) and searched for at least an hour each time to no avail. We logged our DNF's and moved on, almost certain it was gone. We returned in June to give it another try, same results. This time, my better half requested maintenance on the cache since it was missing. About a month passed with no update in the log on the cache. At that point, I sent the CO a message requesting help on the cache to see if we were looking in the correct place. I have not yet heard anything back from that.
My second example is from a cache I tried to find more recently in a city park. This one is also a 1.5/1.5, but I was not able to locate after searching for 30 minutes and using the hint. Additionally, the 7 logs before mine were DNF's, starting in June. I have not logged a maintenance request or contacted the CO on this one yet.
So, here is my question: What should I do now? I know there are several routes I can take:
-Just forget about it and move on
-Continue to try and reach the CO
-Log a needs archived. I am hesitant on this one, because I feel like it may not be my business to get the reviewer involved. And I'm not sure if enough time has passed to get them involved.
I am not sure why this person isn't checking. They may have personal stuff to attend to or something. I know they are experienced with over 10k finds and over 100 hides.
If anyone could provide advice on how I should proceed, I would certainly appreciate it.
Thanks
-
I would think mailing the TB would go against the "natural" progression of the TB. The idea is to move from cache to cache with a cacher, right? Not USPS or whatever.
If any of you were part of wheresgeorge.com back in the day, it was the same concept. You wanted the currency note to travel naturally. Otherwise it's false travel.
Just my thoughts.
Suppose the UPS guy is a cacher?!?!?!
Mind. Blown. haha.
-
I would think mailing the TB would go against the "natural" progression of the TB. The idea is to move from cache to cache with a cacher, right? Not USPS or whatever.
If any of you were part of wheresgeorge.com back in the day, it was the same concept. You wanted the currency note to travel naturally. Otherwise it's false travel.
Just my thoughts.
-
TB
in Trackables
I think only the CO can remove them? I'm not totally sure. We have only been doing this for a year, but in that time have learned not to seek a cache just because it says there are TB's inside. Most of the time (in my experience) there are none.
On a side note, it is always fun to find TB's when not expecting them.
I doubt that helps, but it is my two pennies!
-
Empty shell casings from various handgun calibers. Food of any type. I try and clean up those caches.
I really like bullet casings. I would love to find those in acache.
I've thought about leaving them in caches before, but worried it would fall in the offensive category... I guess anything could fall into that category depending on a person's views.
-
#1 A very corroded 410 shotgun shell. Do you have any idea how difficult it is to get rid of those?
#2 A bunch of Party Poppers that were in a cache that had been wet for a loooong time. We actually wound up adopting that one, no more wet party poppers there
Around here, those shells are used for "Y.A.R.N.S." (Yet another road to nowhere) They are put into the sides of barricades on dead end roads. Usually they are not left in other caches though...
-
I have one to add to this. A lottery ticket. More importantly, a used lottery ticket. Even more...a losing lottery ticket.
And then there's the one we found today. A winning lottery ticket. A winning lottery ticket that was worth $500. A winning lottery ticket that had yet to be claimed.
So we cashed it in.
Only to find...
It was a winning lottery ticket that had expired over two years ago.
I laugh about it, but that means somebody was sitting on a $500 lottery ticket that was never claimed.
That's just a slap in the face!!
-
a beer cap
I've been finding a lot of beer caps lately in caches. Maybe it's a San Diego thing.
I've thought about doing that for the local crafts I enjoy... maybe not since it could be considered "offensive".
Craft beers that is...
-
Not me.... I fish, camp, and Geocache in the winter.
fish...maybe. Camp? No way jose. I would be frozen in the morning! haha.
Fundraiser coin for the Historic Mansion of the Saltine Cracker Inventor
in Trackables
Posted
I certainly would like one as well. Can't wait for them to go on sale!