GOF and Bacall

I think you pretty much have your answer. Linking to non family friendly pages is, in the eyes of GS, not family friendly. The podcast you link to is not family friendly even if it has a not offensive home page.

Where is this fabulous ignore button that you speak of? Go on the cache page and where you log a visit you will see the Ignore Listing right under log a visit. I think the question was how to ignore the hider. Well how else do you expect to ignore a hider? You go into their caches and ignore every single cache they own. You see how that works. Which does no good if they post new caches... You're kidding me, right? I'm sure when you see the name of the CO you will add that cache to the list as well. This isn't rocket science here. Maybe not rocket science, but Groundspeak giving us the ability to simply exclude all of a users caches from our PQs must be. BTW, I have almost 500 caches that I would like to ignore by a particular hider, and he's hiding 20 a week. It sure would be nice if I could stick his name in a box, click OK and be done with it. Oh, I agree it would be nice to be able to block a hider, but in the meantime you have the ability to ignore one cache at a time. At least you have something to work with. Hey, it gives GS something to work on and players something to complain about. Perfect harmony. Except GS is not working on it. Quite some time ago Mr. Irish stated, if I recall correctly, that it was on the list of things to work on. But when pushed it was admitted that this idea, with several others that users have been asking for, where so far down the list that they were unlikely to ever get any attention from the developers. In other words, fogettaboutit!

You can start by checking out Markwell's PQ tutorial. It will help you understand how PQs work. Then you will want a program to help manage the results from your PQ. There are several. I recommend Geocaching Swiss Army Knife, or GSAK for short. It has a bit of a steep learning curve but it is so useful that it is well worth the effort and small cost.

Try logging out and then logging back in to your GC account.

Original owner had permission. I am going to call the park and re-ask, for mine. Thanks everyone. Be aware that many caches get archived because the location is somehow now 'compromised' such that a cache won't last long there. Maybe not in this case but it frequently happens. One more reason not to place a cache back in the exact same location. Goes right along with trying to give the cache seekers something new to find. Something different than what they found last time. It isn't easy, but worth the effort.

It is not the cache owners responsibility to worry about others side games (such as completing the grid). My responsibility is to the finders, and to that end, I will make sure the D/T are as good as can be expected. Have a changed D/T often? No. But it has happened. Precisely. If you want to play a side game such as filling a grid, caching on all 366 days, etc, that is up to you. D/T were not created to fill a grid. They were created to tell a cacher what to expect about the hunt for a cache. The "grid" came along with GSAK, etc, and became a side game with folks creating ALR caches like the "challenges" we still have today. Again, if your grid changes, and you feel the need to keep it all filled in, find some more caches. Nice attitude, I'm gonna do what ever I want and don't care one bit about what anyone else thinks or how my actions may affect them. Luckily for me in my 2 years of geocaching I have never met a person with this attitude in real life because if I did I think I'd be sickened enough to find a new pass time without people like that. I believe this is the same comment you made the last time this came up. I care about finders (which are the people that count in my eyes). Not people playing a side game. And if you look at my caches, and the positive feedback and numbers of favorite points, you would see I care very much about cachers. If you have a rare D/T combo chances are most people finding your cache do so for the rating and changing it obviously shows you do not care. If a cache changed drastically enough like a road being built eliminating a long, tough hike the right thing to do would be to put out a new cache and archive the old one and if it was a minor change why mess with it at all. Submitting a new listing is one option. I agree that if a cache experience changes significantly it makes sense to create a new listing. Others argue that there is never a good reason to archive a cache just to create a new one in the same place. The ratings are for informational purposes. They were created to let users know what to expect when they hunt for a cache. They were not designed to fill out a grid for a challenge. They should always reflect the conditions of the cache as accurately as possible. It is not a matter of not caring about the people who play the side games. I can understand your frustration. However, conditions change and that is a part of the challenge of filling out those grids. We wouldn't want to make it TOO easy. They wouldn't be challenging.

I generally give equal opportunity to every cache on an individual basis. If it's a crappy cache in a crappy location, hopefully I find it quickly and never need to go back again. That being said, there ARE a few 'locals' who have a proven track record of nothing but uninteresting (to me at least) caches. I have a GSAK filter to sort out caches by these hiders, and I can then add them to my ignore list with the API. And every time they hide a few new caches you have to go through the whole process again, correct? Wouldn't it be easier to simply tick a box on the users profile page once and never have to deal with it again?

I have long asked for an ignore all by user feature. We have several users around here that do not see caching the same way as I do. There is nothing wrong with that. But such an expansion of the ignore list feature would just be one more tool to help any player maximize the enjoyment they get from this game. They could ignore my caches just as easily as I could ignore theirs. This is a very good, if extreme, example of why it would be such a useful tool. Yes, we could go through and add each listing manually. But it would be an onerous task. Such a tool would only improve the enjoyment users get from this game.

Bad idea. If you can't maintain them don't hide them.

I just posted this response to another thread. I think it also fits here. I think the ratings should accurately, as close as possible, represent the difficulty of the cache. If something changes that effects that difficulty the ratings should be changed to match. The ratings are not there to help fill out the grid for challenges. They are there to inform people how difficult the cache is to approach and to find.

I think the ratings should accurately, as close as possible, represent the difficulty of the cache. If something changes that effects that difficulty the ratings should be changed to match. The ratings are not there to help fill out the grid for challenges. They are there to inform people how difficult the cache is to approach and to find.

We love the pennie smasher machines, and collect smashed pennies. The old wheat pennies work best, they are copper and not zinc like the new ones. They do make good trade items. Actually, anything up to and including 1981 will give good results. That is when they went from 95% copper to 97% zinc.

I wonder what the percentage of cacher that have the gear and know how to actually do a technical climb is? How does that compare to the percentage of caches that require such a climb? I suspect that the numbers, or lack there of, are related.

Bingo. Dang! All I needed was G47.

Google Translation. I always place the cache first. But that doesn't mean you couldn't fill out the form first. Just make sure that the cache is in place and ready to be found before you enable the listing. People will be unhappy if they go out looking for a cache you have yet to place.

That was my thought too. Hide the cache you want to hide, then describe its size/terrain/difficulty accurately when you list it. Starting with the size/terrain/difficulty rating and then trying to come up with something that qualifies for the desired rating seems completely backwards to me. Agreed. List what you hid. Do your best to be accurate.

Actually I think there are three things in that post that would each keep a thread going for some time. The elitist angle. The bully thing. The deleting of spoilers.

I always trade what I think it's worth.

Yeah, I gotta agree. This player seems to have come and gone in a very short time. I would consider the cache in question abandoned. But normally I would recommend putting a bit more effort into being sure that it wasn't listed elsewhere. Like a letterboxing site or one of the other geocaching sites. I know we wouldn't like it if say a letterboxer assumed that our game pieces were trash because they couldn't find a current listing for it on their site.

That is the only way you CAN log those caches.

As often as I have complained about the lack of communication from TPTB I am feeling a bit sorry that I have taken so long to thank Bryan for coming in to this conversation. It is refreshing to hear what's going on from the GS perspective. I agree with Radioscout. should cover it. If Deskdata signed the log book in the cache he should be allowed to claim the find. I look forward to this being resolved.

Personally I think it reasonable to expect a cache that is wheelchair accessible be accessible from a wheelchair. T1D1 has been expected to be wheelchair accessible way back to before I started playing. But I will agree that the guideline could be a bit more explicit on the subject.

Unless they belong to TheWhiteUrkeler, Mr.Yuck. I'm gonna go out and take all his caches and replace them with leaky film cans and gasketless blinkies.

Huh, you're listed in the PM group...flying under the radar? Not sure why that is. But it isn't something I'm doing. At least not that I know of.

You should break this post out into its own thread. It would be longer than this thread in no time.