^up

I carry a .357 as needed :-) ….cause the .50 cal. just won't fit in the bag.

boils down to two camps: Those that feel the need to be first to find to prove something to someone else versus, those that are satisfied with proving something to themselves.

Why I won't recognize any FTF folks on my pages unless I know them to be law abiding and didn't act inappropriately. I don't think I've had any on my hides yet, but I simply don't know. Probably change once I get to know some other geocachers.

Could be experimental and more prone to failure.

Yeah, this irks me too. I recently saw a log where someone looking for a D/T 4/4 couldn't find it and said they were replacing the container because it's obviously not there and they need a smilie for my "Fizzy" grid. For real? Some egos are just too big for this game! The most annoying part is that the next hunters have a cheapened experience. I'm working on some really creative hides now, which I'm sure folks will miss, not find. Then, someone from out of state comes and makes a find of some cheap container and I have to delete their log because they did not find the cache, but they don't really have a chance to return. This is one of those grey areas. I'm not condoning the throw down at all but I wouldn't be so quick about deleting a subsequent finders log. Lots of geocachers search for caches without reading the entire description, and there isn't anything in the guidelines which mandates that one must read the cache listing before finding the cache. I've found 4 star difficulty caches within two minutes upon arrival at GZ a few times. Sometimes you just get lucky. If the subsequent finder didn't know that it was a 4 D cache (and some caches are way overrated) they might not even realize that they found a replacement rather than the original. Since over 10% of my finds are on caches over 1000 miles from home I'm well aware of what it's like to cache from out of state (or country). That's way I always trying to find at least a couple of caches when I visit a new country. Personally, I'd delete the log on the throwdown, and send a PM to the subsequent finder to let them know that they found a throwdown rather than the actual cache and *suggest* they might want to delete their find. If the didn't, I'd let their log stand. I'd know that they didn't find the cache, and *they* would know that they didn't find the cache. If they choose to convince themselves they found it, it doesn't effect me at all. I would be worried about annoying some fellow cachers, but I'm not worried about breaking any rules by deleting the logs. The rules say they have to sign THE log, not ANY log. By technicality, the throw down is a cache that was placed and violates the proximity rules and therefore is not a valid cache.

Does this mean I need to list a cache at my washer and drier?

In Russia, Power Trial does you! Just kidding. Getting ready to do my first too. My geo-buddy and I are going to do it together so it is a little more manageable. I'm gonna drive because I don't really mind not being the actual finder. I will be logging/searching for ideas though, so not gonna rush it.

Would have the ability to request the company with the software to make that change. Surprised it isn't an existing feature as it is with the two other forums I'm a member of.

I will be in the area on Sunday so I can drive by and see if it is theirs or not. If it is I wish the COs would say so on the cache page. In front of the other houses it won't look good to see strangers poking around the tree and being near the Day Care Center. That isn't a property plot plan, and other than seeing who owns the property, it shouldn't be used to assume where the property lines are. Often times property lines stop at or near the sidewalk. Do agree that it would be nice to have the cache owner say where or not it is on private property or not. I have done such on my caches, but they often are adjacent utility right-of-way.

Could do a cache of caches. I did this for one cache. I placed a cache in a nearby, but different spot. If the cache ends up needing maintenance and has to be deactivated or archived, I can switch to the back up. The back up is labeled as "back-up" so as not to confuse a finder (though it is about 50 feet away). This allows me to not have to visit a far off cache immediately. I can switch back once I visit and restore the original (or make the original spot the new back up). Point: there are all kinds of ways to work maintenance and longevity into caches. Creativity is part of the game. I get that many enjoy team work and a sense of 'community' but one has to have personal responsibility and accept limits of their abilities.

Yeah, this irks me too. I recently saw a log where someone looking for a D/T 4/4 couldn't find it and said they were replacing the container because it's obviously not there and they need a smilie for my "Fizzy" grid. For real? Some egos are just too big for this game! The most annoying part is that the next hunters have a cheapened experience. I'm working on some really creative hides now, which I'm sure folks will miss, not find. Then, someone from out of state comes and makes a find of some cheap container and I have to delete their log because they did not find the cache, but they don't really have a chance to return.

Throw-downs! Those erk me the most. If you didn't find it, replacing it with your own isn't getting the smiley. You failed to find, therefore it isn't a find. If you want to help then ask the cache owner first. I am OK with extra paper for logging. But personally my caches are new, and not an issue.

I've gotten caught by the proximity bit too and feel your pain. Not knowing the nature of the cache, is the spot so significant that another 120 or so feet makes a big difference. Mine aren't so special so I just adjusted. But I also create the cache page before I even visit the area (unless I found a neat spot while I was out). Once the cache page is created (with some ball park coordinates) you can do the "find nearest caches" and the list will include ALL caches with distances. Solves the whole proximity issue fast.

If a power series is too much for a single person to handle, then have partner(s). That is what I do...and maintain caches in two states this way. But this is because we both have visited each cache and know exactly how each is suppose to be hidden. Problem with and hunter that puts a throw-down is they don't know the subtleness of the hide or may not have the unique container that a hider uses.

I do not want anyone doing anything to my caches but find them. Already had an issue with "throw-down" cachers so called replacing a missing cache and five other cachers logged that terrible replacement rather than my creative one, cheapening the point. DO NOT MAINTAIN ANY CACHE BUT YOUR OWN. If you find an issue, only log a DNF and/or Needs Maintenance. If you want to help fellow caters, create an event that assists in getting supplies to fellow cachers.

We are saying this is an issue for a travel bug or coin of from someone else. I was thinking about getting a vehicle travel bug to track my own mileage. That would require a visited or dipped, or whatever it is called, log. That wouldn't be an issue right?

Stranger Danger Stranger Danger Sorry, just had a 1980s flashback

Knowing you were associated with this one makes me feel inclined to say it was published fairly. You have been more than fair with my caches in Florida.

did you actually use all those?

Can't go wrong with a Garmin

Understood, but it helps, and the problem can't be nearly as bad as the complainers here want others to believe. I just don't buy it that this is a rash problem that needs ointment. I personally can see requiring an email, but I hate email and pretty much ignore it anyways, so what is to say others won't just use a fake or spam only account if it is required. BTW, I'm generally voting for just leave it the way it is.

Remember, they are guidelines and not rules. At least that is what I read in other forum posts. I think that means you can bend the rules somewhat, but more of a case by case review and depends on the reviewer. Some more strict than others.

Of course, cache owners could just put a link to a short @gogeoaching video (like this one on youtube) on the top of their pages if they are worried about new users. I suspect any new user would fairly quickly open and watch the video, which is better than being completely in the dark. I just quickly picked this one, you can pick or create your own.

OK, "Archive it" (gmail) is the same as putting it in a folder then. I was worried that was going to delete them. I'll try that. I thought about another account, but I really don't like computers or spending much time on them and that seems like more complication. I've spent more time on the computer with geocaching already but it is fun. I just want simple, basic, things. I understand the point about being ignored, but I'm more likely to ignore emails altogether. Using the app on my iPhone 99% of the time means I see the logs there much sooner. So far, in the months I've been doing this, the few maintenance items that have come up were dealt with quickly and I never even read the emails. Of course, I know that isn't a guarantee for the future. But I think I know myself pretty well. So, just to confirm, there is no settings on this site to stop the notifications. I have to filter or control it externally. BTW, mine are only a "Power Trail" because I put them under power lines. Most are separated by .3 or more miles. I'm almost done with those and the next few won't be a series at all. The fun part for me is the hiding. I'm not so interested in finding them.

Definitely not. If the trackable says it does not want to 'visit' caches, then that is not a valid log, and should be deleted. A cacher who spends four months 'visiting' the trackable to hundreds of caches in Belgium is the one who is violating the guidelines. Do not 'visit' means 'do not visit this trackable to caches.' Maybe I'm missing something. I thought an owner couldn't dictate that kind of rule. I'll have to re-read the guidelines again when I get some time. I certainly get that one shouldn't keep the trackables, but I'm not sure I get why visiting a TB in a cache is so bad. I thought the point is for them to travel. But still new and haven't done one yet, my own or another person's TB.