ZeekLTK

It depends. If we are traveling and just looking for a quick cache in order to get a find in a new area that we would otherwise never visit or stop in (aka, just driving through), we typically just pull up the app and look for the closest cache off the highway. All we check is the "recent log" list to make sure it's actually there. If needed, we'll look at the "hint". Rarely will we look at the description; just don't have time for it in those cases. I'm much more likely to read the description if I'm using the website to look up caches beforehand or even after the fact; if I didn't log it on my phone and now I'm back at home logging everything on the website then I'll finally read the description at that point, even though I made the find several hours earlier. If you really want people to read your description, make it a puzzle or multi-stage cache - so that it will not be possible to find the cache without reading the description.

I don't think that's "OK". DNF is supposed to help warn people that "hey, maybe this thing is missing" and if there are enough DNFs in a row, "hey, maybe the owner should go check to see if it's actually there". So if you looked for it and didn't find it, log the DNF! Plus, by not logging a DNF you are wasting other people's time. I will not go to a cache if the last 4-5 logs are DNF, so then I won't be looking for something that (probably) isn't there. I imagine there are plenty of others who check for DNFs before going to search. If no one logged a DNF though, how would I know to avoid it? Be considerate of others and log a DNF if you couldn't find it!

The person who finds it will log it and will "take possession" of it. So just be patient, the problem will solve itself when someone is pleasantly surprised to find the trackable in the cache that they weren't expecting.

I used to find and move trackables all the time in like 2010-2012. I started to find fewer and fewer in 2013 and I honestly don't think I have seen a single one in the last 2 years.

How inexpensive/accessible are RFID chips these days? I feel like we should be at the point, or at least approaching it, where it would be feasible to put some kind of chip in the container of a cache so that you can track it if it does go missing. I've only just thought of this though, so I've never looked into it. Wonder if anyone else has?

It's not always so simple. In 2013 we were preparing to move from Michigan to Maine. So I grabbed as many travel bugs as I could find to bring with me, as that would help put a lot of miles on them. Once we got to Maine, I put the travel bugs in various caches that we found. However, after I placed the last one I realized that my list wasn't empty, it said I still had one more left to place. I just couldn't find it anywhere though, must have gotten packed into another box. It's been almost 3 years now and I still haven't been able to find that darn bug. The site still lists that I have it, and I'm sure I do. Where exactly, that's a tougher question to answer. I always look for it when we go through a box that hasn't been touched in a long time, but unfortunately it just hasn't shown up yet.

Meh, it happened almost 3 years ago and the cache has since been archived (I wonder why? lol).

It's hilarious how mad some people get over a perceived slight of an NM log. We once found a cache that had a completely full log book. Well, it was full after we signed it. I logged the find saying: "Easy find on the way up to XXX. We used the very last spot in the log though - it's completely FULL now!" and then logged a "Needs Maintenance" just saying: "Log book is full." Seemed simple enough, just letting him know he needs to go replace it soon. But a few days later the cache owner then sent me a very nasty email, very upset that I had logged a "Needs Maintenance" and basically telling me that I should just replace the paper myself. Pretty sure that's not my job... Then, 12 days later, the very next person who found it also logged a "Needs Maintenance" saying the same thing: "Log is very full needs replacing." I wonder what kind of email that guy got. lol

You also have to consider that once someone has found a cache, they aren't going to try to find it again. As time passes, there are simply fewer and fewer people in any given area who haven't already found the local caches. At that point, the only way someone new would look for the cache is either if another local started geocaching or, much more likely, a geocacher from somewhere else is passing through AND has the time to look for your cache. Since most traveling geocachers are typically on a time constraint, a lot of them simply won't be able to attempt to find a good hide that takes a while. They'll opt for something quick and easy so that they can continue going where ever they are headed. For example, when we drove from Florida to Maine, we made sure to get a find in each state. However, we also made sure to try to go for the easiest possible finds, because we weren't about to spend 2-3 hours in Georgia looking for 1 cache, or multiple caches if we wound up with some DNFs. We just wanted one that we could find on a 5 minute break and then get back on the road so that we could get to Virginia before midnight.

Also I will speculate that the reason this is so important is that the OP has one of those tracking devices on his leg and was not allowed to leave the town of Newark. So he saw this specific cache pop up which said that it was in Newark, so he was excited that there was finally a new cache to find in his limited area of mobility. But once he got to the GZ his device went off and he discovered that he had violated his probation because it was actually not inside Newark! After 5 more years in prison, he is finally back out and is still furious that the thing that did him in was some guy carelessly writing "this cache is in Newark" when clearly, based on the events that unfolded when he visited the cache, that is not accurate! Sorry for the bad luck OP! Did you at least find the cache before they found you? Or did they at least let you log a DNF before taking you in?

I mean, things like mentioning the wrong town (and only "technically") I don't think are that big of a deal. But I wish people would pay attention to the geography when placing caches near borders. There is one cache that I found on the Michigan side of the Michigan-Indiana border, but the owner incorrectly marked it as being an "Indiana" cache. So now on sites like project-gc.com my stats are slightly off, since it counts the cache as what the owner marked it, rather than where it actually was.

Sure, recurring $30 > $10, but $10 + ad revenue > $0. $0 is what you get when your app sucks so much that even though it is the "official" app, people still don't use it (such as your example). So Groundspeak isn't getting $30 recurring payments, they are getting passed over and people are downloading other apps that work better. Those other apps are getting the ad revenue that Groundspeak COULD be getting. So what is the point of hiring those expensive developers to create an app that your primary target demographic (people who want to geocache) are not going to use? IMO the 1.5/1.5 restriction makes absolutely no sense because, as others have pointed out, anything other than a lamppost cache is generally higher than that. We've been caching since 2009 and were without our phone for a weekend, so we tried to download the new app on someone else's phone to use, only to find out that it was essentially worthless because of the restriction. Every single cache we had planned to get that weekend was higher than 1.5/1.5, so we couldn't use the app to find any of them! We immediately deleted it and downloaded a different app instead. So what is the point of it? Why not make an app that people will actually use? Are there that many people who do pay the $30 to make an app specifically for them? Because I just don't see how a non-paying member would ever find this one useful. And that means Groundspeak is missing out on a huge demographic that they could at least get ad revenue from, and instead they are channeling those people to other apps, and by doing so they get absolutely nothing out of it. Because previously, you would always hit something on Groundspeak - either the website or the app - to log a cache. Now you can completely skip interacting with Groundspeak at all by using these other apps and still geocache. By having this restriction on their own app, they are basically encouraging people to skip interacting with them. To me, it doesn't make any (financial or logical) sense. They should want to be the primary source for geocaching, to get all traffic to come through them, but this is doing the opposite, it's pushing people away. *Edit: lol, it automatically capitalizes the word Groundspeak. Interesting.

Usually this happens when logging from the app. Out in the woods, service isn't great, so sometimes it looks like the log did not submit. So you click submit again and finally get the confirmation screen... and then later (if) you look at the cache on the website you see that it posted both times that you clicked submit.

The guy sitting in the car could have been a geocacher waiting to make sure there weren't any muggles around - and then he saw you, assumed you were a muggle, and continued to wait. Or maybe he actually had the ammo can in his car and he was in the process of signing it?

You can always take matters into your own hands and "muggle" the cache yourself, then report it missing and hope the CO is too lazy to replace it.

I'm not sure what you expect them to do. The point of a trackable is that if you come across the tracking number, you can go online and put that number in to log it. There is no way that the website can determine HOW someone came across that tracking number in the first place. There is no way to know if someone parked next to you and took a picture of the number so that they could log it later, or if someone came across that picture and also decided to log it, even though they never saw your van in person. As far as the code/website is concerned, they are both doing the exact same thing: typing in the tracking number. If your number is out there for anyone to see, then I don't understand getting mad when people log it. I have a travel bug that I use just to track my own personal miles and I have never had someone else discover it, because I've never shared the tracking number with anyone. Those seem to be the only two realistic options: either never share your tracking number with anyone, or do share it and assume that anyone in the world will be able to find it.

I recently noticed that the description of the Michigan state badge says: The "Wolverine State" is comprised of two peninsulas, the Lower Peninsula and the Upper Peninsula. It is famously the heart of the American car industry. Michigan has the longest freshwater shoreline in the world. The issue is that it uses the term "Wolverine State", which is incorrect. The state's primary nickname is the "Great Lakes State", as seen on the national currency that was created back when a quarter was made for all 50 states. The "Michigan quarter" uses the official nickname: Is there any way this souvenir description can be updated to use the proper nickname?

Unprovoked "nasty" emails from a cache owner to a log are usually never helpful. I came across a micro in which the log sheet was so full that I basically couldn't sign it. Just had to scribble my initials partially over someone else's signature (since it was a cache several hours from where I live, I couldn't just wait and come back another time) in order to get it on there. When I got home to log it, I noticed that the last 2-3 logs had also mentioned that the log was full. Since several weeks had passed since the first person had noted that, I logged a "needs maintenance" to get the owner's attention. Rather than going to replace the log, he sent me a nasty email basically saying that if I was so concerned about it, I should replace it myself. lol And what's the big deal? You put a cache out, then you're mad that you have to maintain it? lol

It's gotten ridiculous how much people cheat in order to say they got a "FTF" - it pretty much makes it meaningless IMO. For example, I was browsing caches in my area to go find and came across one where the guy literally wrote that the only reason he placed it is because his friend had a streak going (had at least 1 FTF every month for [however many months]) and it was almost the end of January and the guy didn't have a FTF yet, so he was placing the cache just so his buddy could log a FTF on it. At that point, how is such a streak even worthwhile if you have to cheat to keep it going? Is that really "fun"? I would have loved to read that someone else got a FTF on that one, and the guy's streak ended anyways (lol) but I bet the log was already signed before it was even published. So lame.

I found a similar series a few years ago. This was the one I found, I took it from Michigan to Maine to help it win the "first to the east coast" contest. http://www.geocaching.com/track/details.aspx?tracker=TB420KH I never did find any of the other ones.

I started geocaching in 2009, and although I never found a ton of caches (I just passed 200 total this year), I seemed to find a travel bug fairly regularly (in fact, I think that was the aspect that got me "hooked" - I'm always traveling, so I liked taking one with me and dropping it off in a new state). But lately, in the past year or so, I've noticed that I'm not finding hardly any TBs any more (I haven't found one at all this year yet! And I've found more caches this year than I have in any other year before!). Are there just not as many out there? Or are there so many geocachers now that they just get taken immediately when they get dropped in a cache? It's also difficult to even see what caches actually have travel bugs in them, because lots of caches are marked as having a travel bug, but they don't actually have one. I think this is also making it harder to find them, because you can't even reliably look for the "has TB" icon - it's usually a false positive. Has anyone else noticed this as well? Any idea why this is happening?

GOAT = greatest of all time?

That's not true. I sometimes cache with my wife. We each have our own accounts. I'll write up my log for the find (using the word "we" to describe what happened) and then, instead of repeat the same thing, she'll just log "TFTC". Just one example, at least, of using that while not meaning to diss the cache. In fact, I would rather people just post "TFTC" instead of copy/paste a long winded, yet generic, explanation about their whole trip that they put on EVERY cache they find that day - which usually has no specific info about the actual cache(s) they post about. "Today we left at 6:30 AM and drove 200 miles up the coast. It was a lot of fun to see everything and find a few caches along the way. This was one of 36 that we found today" - is, IMO, a much more boring/worse log than to just say "TFTC", since it has absolutely nothing to do with the cache itself. It is especially annoying when you see the exact same log over and over again on all the caches in a certain area. If you don't have anything to say about the cache, or you did too many too remember them individually, then just write "TFTC" and move along.

I've been using this: http://itouchmap.com/latlong.html But you do have to convert to either DD.DDDD or DD MM SS

[same guy decides he wants a smiley anyways despite the NM he just posted] Found it 08/06/2013 Missing [another call for CO to check] Needs Maintenance 08/06/2013 Found string no cache [guy thinks string is good enough] Found it 07/28/2013 Found the string, no cache [same noob tried to change his log to DNF but posted another instead] Didn't find it 06/19/2013 string is there, no cache. [noob found string] Found it 06/19/2013 Dnf, found string [another guy confirms missing cache] Didn't find it 06/04/2013 DNF. Found the string it was attached to. Owner should check. [guy who alerts everyone it's missing] Needs Maintenance 05/18/2013 It's missing :-/ Someone else posted as missing-here's the proof (a picture) [First to notice missing cache] Found it 04/26/2013 I found the location but it appeared to be missing.