4wheelin_fool

That's all. Just 'Thanks.' Anyway...so I go back a week or two later and find it in a spot that is much further from the trail than the hint says it should be. I decide I can't help myself and in my found it log I say "The only thing that bothers me more than a find the day after I post a DNF on a cache is when all that log says is "Thanks" or "TFTC". That's all I will say about that." The cache wasn't missing and you were able to find it. Plus, the one word logger was able to verify it was there for you, and likely left it uncovered for you out of laziness. You may want to thank them. Not the point...but it goes back to the whole issue of logging "TFTC" or "Thanks" or even just a "." and other such meaningless stuff. It's all made worse when it's the day after my DNF...like salt in an open wound. A DNF should not be like an open wound. You were there and looked, that's all. If there was nothing otherwise nice about visiting the area, you probably should not have bothered looking in the first place. Personally I wouldn't care if a knucklehead found it after me, as it's likely that another knucklehead hid it, and there is probably some form of knucklehead code in the listing that I missed, and wouldn't want to know too much about anyway.. Don't trivialize something just because others dislike DNFing more than you. I find a DNF to be something of a failure - minor as it may be. I still log them, but they are made all the more embarassing when someone with 20 finds comes by the next day and logs a find. Its an opinion, which is what forums are for. Equating a DNF to an open sore is a bit extreme and likely why people don't post their DNFs. Personally I don't really mind not finding one, as it deepens the mystery and makes any return visit more interesting. An easy find is often forgettable. Being embarrassed over a DNF is taking it way too seriously, in my opinion.

and here I've only been charging $30 for climbing lessons. What a sucker I am. Yeah, that's also going to cut into my business once they figure it out for themselves. How about hiding a few 5/5s, laughing maniacally, and not answering the phone for a few weeks?

That's all. Just 'Thanks.' Anyway...so I go back a week or two later and find it in a spot that is much further from the trail than the hint says it should be. I decide I can't help myself and in my found it log I say "The only thing that bothers me more than a find the day after I post a DNF on a cache is when all that log says is "Thanks" or "TFTC". That's all I will say about that." The cache wasn't missing and you were able to find it. Plus, the one word logger was able to verify it was there for you, and likely left it uncovered for you out of laziness. You may want to thank them. Not the point...but it goes back to the whole issue of logging "TFTC" or "Thanks" or even just a "." and other such meaningless stuff. It's all made worse when it's the day after my DNF...like salt in an open wound. A DNF should not be like an open wound. You were there and looked, that's all. If there was nothing otherwise nice about visiting the area, you probably should not have bothered looking in the first place. Personally I wouldn't care if a knucklehead found it after me, as it's likely that another knucklehead hid it, and there is probably some form of knucklehead code in the listing that I missed, and wouldn't want to know too much about anyway..

That's all. Just 'Thanks.' Anyway...so I go back a week or two later and find it in a spot that is much further from the trail than the hint says it should be. I decide I can't help myself and in my found it log I say "The only thing that bothers me more than a find the day after I post a DNF on a cache is when all that log says is "Thanks" or "TFTC". That's all I will say about that." The cache wasn't missing and you were able to find it. Plus, the one word logger was able to verify it was there for you, and likely left it uncovered for you out of laziness. You may want to thank them.

You could have your geofriends that live in the area adopt it before it is put in the queue, that way it would likely get published. If it is nothing but a bison tube, you could also hide 2 others some 60 feet away. That way if it goes missing, you could do some instant maintenance from Alaska by just changing the coords. However the problem with bison tubes is that the rubber O-rings rot away, sometimes within a year, but usually in wet conditions or direct sunlight. You may want to leave a pill bottle nearby with spares.

Dont know if animated gifs in cache logs are a good idea anyway.

I charge $50 for 5/5s within 50 miles of my home coordinates. Outside of that the prices go up, however it's the cheapest in the area. I think iPod guy charges $80 or more.

The cache was archived due to the HOA posting a NM, but with the archive log backdated a day, it could be interpreted that it was done as a result of something.that went on behind the scenes, such as permission being rescinded. :ph34r: Okay I checked the email. It was archived on October 9th at 2:41PM, but it appears that the archive note was dated for October 8th at the time by the CO. I didn't think that archive notes could be backdated, but apparently they can. I don't know why such a thing would be allowed either.

That's really odd. It was archived on October 9th, the same day as those finds. Now it says October 8th. I am 100% certain of this. Notice the Needs Maintenance log posted by the HOA? Its dated October 9th. You cant post a Needs Maintenance log on an archived cache. This means that the archive note was edited at some point to reflect an earlier date, and not by the CO, or it would have an edit line. :ph34r:

Well that speaks volumes. Either by misunderstanding or plain deception, the cache owner added the reviewer approval bit to validate the practice. Guess that never happened. The multilogging of the traditional is mentioned on the event page, but even that has multilogs as well. Looks like 30 some people went and posted 660 attend logs.

At one time geocachers used to write a full page in the logbook when finding a cache. Today, they just sign and put anything of interest online, but even that is slowly disappearing. This cache is just filled with nonsensical logging. Being that some geocachers love numbers, I predict that this trend will spread now that it has crossed over to traditional caches and the unique designation has disappeared from profiles. It's starting to resemble the QR code scanning game more and more every day.

+ 1.....$50 + hide X amount of caches + X amount caches found = experienced cacher and IMO the type cacher I want handling my caches and TB's......I'd change all mine to PLATINUM ONLY CACHES.....also need to lock it down, eliminate back door logging, etc. Lets cull the herd folks. First the listings were spammed with senseless disposable micros, and now the site is being spammed with app using muggles. Another tier would not hurt a bit.

It means Simple Logger. <snip> Huh, I thought it meant "Signed Log". At least it does around here... Signing the log is a normal part of the game and it's redundant to mention it. Now if someone insists on writing a two character log about something that they should be doing anyway, that pretty much indicates a Simple Logger.

Short answer yes. That's it? Not that much snow for how cold it is in Minnesota.

There's adequate permission which is often assumed if the land is open to the public. Then there are instructions to disregard signage based on intentional incorrect information, also known as lying. Quite a big difference here. If someone states "I have permission, ignore the signs", and they don't, well...

Why would they mind? The page is already being spammed with found logs. Only certain flavored spam is permitted? Sheesh.

Why would you think anyone would expect you to delete those memories? The sensible thing would be to edit the "find" to a"note".

Tough call. I've seen areas like this and personally wouldn't place a cache there because of the muggle issue. People buy McMansions to get away from "people wandering around like mental patients," or in this case, like people in need of using the woods as a bathroom, which is what the homeowner thought was going on. If geocachers don't care about annoying people, then the result is often that the people may go out of their way to annoy geocachers. Why not go after all of the others, if a characteristic of the geocachers is to be apathetic to the people that live there? I can recall at one time when all geocaches were deep in the woods.

It's Tourettes logging disorder. In this case we have online logging tics. The associated obscene words or socially inappropriate and derogatory remarks symptom is present in only a small minority of people with Tourettes, and in this case only if someone posts an NA.

It doesn't matter whether it's on an event cache, or a traditional, it's just a different flavor of asinine. The difference is that events get archived shortly afterwards and the memories of nonsense logs soon fade. In this example, now traditionals are now defiled with bogus logs. It may satisfy someone's OCD to have the correct log type, but the mental disease is only being spread to a more permanent page to be evident in all eternity. Now the fake logging will seemingly be condoned as eventually others will do the same thing, but not for temporary event hides, but for whatever whim they feel like. There isn't much of a difference between this and pocket caches, except that this is much more stupid. When someone reads a cache page and looks at the logs, they are expecting to see some semblance of what the cache is about, not a storage area for faux scoring points. I can also assume that this is why the distinct caches count was removed from profiles, so that the Tourette loggers can be enabled. They've been doing it for ten years because Groundspeak cannot tell them no, as they are frightened of the predictable ensuing temper tantrum. I can see it now. "Please feel free to log this cache once for every decoy you find, or for every tenth of a mile you drove here, or once for every victim of Ebola". Is it too much to ask to request that these people behave like everyone else on the planet?

It means Simple Logger. TFTC indicates that the cacher believes that they are saving time by shaving two characters off of "thanks", which is longer. TNLNSL means that the cacher has been geocaching since the days when there used to be swag in caches worth noting online or in the logbook.

+1 Walking by someone's house is a bit different than hiding something and extending a public invitation for a steady stream of visitors who might arrive at any time of the day.

I'd like to see them raise it to $50,or at least add a platinum member level.

A cache listing is voluntarily published on a publicly available website designed for cachers to search, share, review, and download cache listings. To then assert an expectation of privacy is a far-fetched. If someone drives by a house on their way to work/school/hobby (once or many times) and see and enjoy the seasonal display someone has in the yard, they are not "peeping toms". However the owner of said display, lurking in the garage noting down licence plate numbers and wondering who drives by to look at their seasonal display X times a day is ... +1 But yet if someone is vandalizing your home you would want to have a camera and motion detected lights so you know who maybe vandaling YOUR home since it was mentioned that you OWN your caches and you want to protect them. In that scenario all of the people that drive by your house are not necessarily vandalizing it. There have been times when someone hides something in a really awful spot, likely to be noticed quickly. Then when it does go missing, they jump to the audit logs and make an erroneous assumption. Exposing the people watching would have the same effect. The only way it could work was if Groundspeak also gave info on who had it in a PQ, as well as viewed it on an app, as well as on a hidden bookmark list, and closed all of the doors. That's what the NSA would do.

I don't see any difference between this cache and the one mentioned in this thread . Both are abusing the log system with asinine, counterfeit logs, other than this one is outlawed and locked quickly, while the other has been practiced for 10 years by hundreds of people. In fact, the logs on this cache are more coherent than the other. As a result it appears that temporary caches are more legit than pocket caches, and the world is full of sheep.