shunra

If I won't be tiring myself out between tomorrow and Saturday in the San Juans, I'll be there too. I haven't yet decided if I'll start from the same trailhead or from another one (there's 4 ways to get to the top!). Don't wait for me...

I found my first 129 caches with a 1999 Magellan Blazer 12, which shows only two digits after the decimal. As a result, the coords were never jumpy, and always spot-on. If it wasn't for the inability to connect it to a computer and for its lack of mapping features, I'd never have needed anything else. Reception of that old Magellan under heavy tree cover was as good as my current Garmin 76S, and better than any Etrex.

Huh?

Cool! I was going to put a cache up there earlier this spring but had to turn back. I was going to try again, but now I don't have to. Same intent, same sentiment

Maybe Sunday you'll feel better? Sunday I might be able to join!

Good point, Jeremy. Since the images are always uploaded at least a few minutes after the log itself, there should be some time stamp checking in order to avoid getting everything twice. I think 6 hours is on the long side (my preference would be 5 minutes), but perhaps this can be individually set - if not, I'll go with the majority here. I like Ed's suggestion of making it a toggle. OK - what if watchlist management allows to click some boxes for every cache, whether you want to receive notifications of: [] logs added to the cache page [] only notes uploaded by the cache owner him/herself [] changes to the cache page [] pictures uploaded to the cache page, if done within X minutes from the time stamp of the log itself. This would actually allow me to reduce the bulk watchlist mail I get, while getting everythign I really want. The default setting could remain just the first option checked, which is the situation right now.

We receive notifications whenever a new Find or other log is added to our own caches, or to the caches on our watchlist. Sometimes, pictures are added to logs at a later date. We don't get notifications of these uploads. It would be nice if we would. In the meantime, when I upload pictures, I always post a note saying 'pictures uploaded', and immediately delete it again. People watching the cache in question would get a notification and could watch the pictures if they want. but it would be better if the notifications would be automatic.

Good point. FWIW, perhaps finders could more often post *their* Reading, rather than just complaining that the coords were a bit off. It would increase the chance that I'd find the right coords among the 4 most recent logs. I'll try to make a point of doing that myself.

I agree with you but still feel that it is up to the finders to provide the TLC. In a lot of cases the owner set the cache with good intentions but has since moved on to other interests. I think that a little more effort by the finders would keep good caches going. Why not take some positive action rather than just posting a SBA? Even bad caches can be revived if the finders are willing to put forth some effort rather than trying to get the owner to meet the finders needs. I don't think finders "should". Finders may, if THEY think the cache is worthwhile. Your whole point (with which I agree) is that the quality of a cache stands and falls with the intent and effort (which is mandatorily continous) put into the cache by the hider. If a cacher has moved on to other interests, there is no question that the cache should be either adopted (formalizing the voluntary TLC) or archived.

Well put. This is why a well-maintained lame cache should not be criticized. It is, of course, very helpful when the cache description would say something about the reason for the hide, or the attraction of the place. This is often the case, but often it is not. Indeed, I'd argue for including an answer to the 'why' question on the cache page. This need only be a very brief phrase ('magnificent view', 'original hiding technique', 'placed with kids for other kids', 'community service to the number boosters', 'unknown landmark of interest', 'surprise!' etc.), and logs could keep the purpose of the cache in mind when giving their feedback. However, an ill-maintained soggy mouldy cache is exactly the opposite, and deserves TLC if it's good, and an SBA if it's bad.

How I recognize that! One thing about deletions that I particularly regret is that they are also deleted from our personal cache history page. If we loose the e-mailed deletion notification with the link to our deleted and archived log, there is no way we can find our own log back. Ever. I would like to have a public place (I imagine it as an unsensored virtual cache) where we could all freely repost logs to, that were deleted from their original location by cache owners who didn't like them for any reason whatsoever. People who lost a smiley could get a replacement smiley here. Cachers who want to preserve a specific memory of their cache history and lost due to some action by a moody cache owner, could post it to that virtual. They could even upload the pictures, again, which would bring those back into our personal gallery. And people who wanted to post a critical comment in a note or a DNF log and had it deleted, could repost it on that virtual, and everyone who would have that virtual on their watch list would read it anyhow. I have run this idea past an approver, but was told that this wouldn't be approved under GC guidelines. I still hope that someone with the power to approve will see the merits of such a cache, though.

אשתי אותו-הדבר טוב, כשתגיעו לאזור שלנו, תהיו בקשר (just testing) æ... extended windows ascii 230 My buck is safe... right? Your buck is safe. It looks good in the part you quoted as well. I never thought it would work in this editor! Initially I copied the text from MS Word, but then I found I could have typed directly in here just as well. The only thing that doesn't work is punctuation, which ends up at the wrong end of the line. So I deleted the exclamation mark. BTW, I apologize for hijacking this thread. I'll shut up now.

Hmmm... Is that a reference to me and Mine? Yep... being a translator, I figured out the coords immediately But I cross the Sound only once in a blue moon, so logging it will have to wait.

אשתי אותו-הדבר טוב, כשתגיעו לאזור שלנו, תהיו בקשר (just testing)

איש ואשה

BTW, I love the way you spell that. How do you do that, in this forum message editor?

Just innocent banter, in case Ish or Isha understands the language of the ishes and ishas. If they don't, no damage done. As to Greek - that's something I understand only once in a blue moon.

Ish, Isha has been a very gracious companion but not what WAS the driving force. She has actually been enjoying going on trips and not having to hear every so often....."We just drove within 1000' of a cache! ishti oto-hadavar tov, kshetagì'u laëzor shelànu, tihyu beqèsher! ( to the rest of you)

You mean you don't!? Now if I could just find a geocaching partner.....since my last one popped. Actually I do! Its just that on the days where we've done 30 caches we just dont have the energy to do it right To stay on topic, I've always wondered about your handle, Ish. I obviously know what it means - see what I do for a living. (or is it the Isha I'm talking to?)

Let me be clear on this, Travisl: I'll try to avoid saying anything negative about the idea of a cache, the choice of location, etc. At the worst, I just won't comment on it at all. Somebody made the effort, thought it was worthwhile, and doesn't deserved to be stomped on, even if I think it is utterly lame and a waste of time. I'll think DBL, but won't say it. However, I'll be scrupulously honest about cache conditions. A mouldy log in a tupperware box will get a comment from me, and likely an SBA as well, if imore people have commented and the owner isn't responsive for whatever reason. I have had some logs like that deleted by cache owners and I assume that some people out there don't like me for it, but this is what I do for the community. Lame locations are in the eye of the beholder, but unmaintained caches are an affront to everyone. A cache owner who makes an effort to hide a cache deserves credit, even when in my subjective opinion his idea is utterly lame. A cache owner who neglects his cache, however, deserves to be outed, if not in public, than at least on his cache page. In either of the two cases, I am not compromising my honesty, but separating my subjective opinion from my objective observations

Good point. If DBL stands for 'Didn't Bother Looking', it might as well stand for 'Didn't Bother Logging' as well.

Sighed log. That's a good one. I prefer to keep my logs positive, though. if a cache owner doesn't 'get it' when he reads something like this: 33/52 of my overnight marathon. I'm getting the hang of this... This also appears to have been my #400th cache, Thanks Nothing will make him get it. And anyway, what would we want to achieve? Do we care if other people go look for the lame cache? Do we want to piss him off? or do we want to stop him from hiding more caches like that? Only the latter, as far as I'm concerned.

The acronym is new, but it changes nothing. We have always been able to leave negative feedback, and traditionally we don't do it. So this acronym won't stick either. Leaving critical logs requires some diplomacy.

I've done it exactly as you said, and it works. That's great! Thanks!

If that "someone else" is also a premium member, then get them to do a PQ of their finds and send that GPX file to you. You could then combine that GPX with yours to produce a GSAK database that combines both your finds and hence you could now do a filter that excludes all caches found by both of you. This solution will work with GSAK now. Yes, she's a member too. So she sends me a GPX of caches she found, I merge that with a file of all the caches I found, and hence have a database of all the caches one of us has found. So far I'm with you. But how do I eliminate the caches in that database from my Unfound-database? You say it's possible, but I don't see how. Hmm. would the following work? 1 - Open her Finds GPX in GSAK, and flag all caches 2 - Load my Unfound-in-the-target-area GPX into the same database, and merge. 3 - Hope the user flags won't get deleted in the course of the merger (will they?) 4 - Filter out all flagged caches Will that work?