kablooey

I am a much better finder when I'm in a group. I think that's because the rest of the group finds the caches that are hidden in the spots that are obvious to anyone with geosense, while my searching uses no geosense whatsoever and thus sometimes locates those caches where the hider is trying to defeat normal geosense.

I have logged 2512 DNFs. I don't log all my DNFs by some people's definitions. I guess mulvaney doesn't consider me to be in his area. I'm kind of surprised that he doesn't consider sdarken to be in his area.

Here are some more ideas: All cache finds are not the same (so presumably your logging of their experiences doesn't need to be the same). So what makes a cache find different? How far did you have to travel to get to the cache? Did you make any wrong turns along the way? How long did it take you to find the cache? Did you find it in the first place you looked? What is the type of container you expected to find? What spot did you sign on the logsheet? Who signed on the logsheet before you? Did you see anything interesting on the way to, at, or on the way from the cache site? Wildlife? Stupid muggles? Somebody talking on a cell phone? In general, when I write logs, I use the log to try to help me remember the experience of finding the cache. Obviously, people who write "TFTC" never go back and read their old logs, though. As a cache owner, I feel like it's my responsibility to make sure that the cache finder has some kind of interesting or unique experience in the process of finding my cache. If my cache is so pedestrian that a finder can park and grab in ten seconds, then I really don't deserve much more than a "TFTC" and I've failed in my attempt to enrichen the cache finder's life. Sometimes I get logs from ride-alongs who really don't have much of an experience, and it shows in their logs. I just try to ignore those people. They're not my target audience. To tell you the truth, most cache owners would probably prefer a note that says "I can't remember a danged thing that was interesting about finding this cache." over "TFTC".

I use "DNS" to mean "Did not search" (in a Note), usually when I reach the location and discover that the park is closed or there are too many muggles in the area or something like that. I usually use "DNF" if I am unable to open the container to sign the log (which has unfortunately happened too many times). I don't trust that I've really found the cache until I can sign the log. I think I may have logged a "Note" once when I did find the cache but forgot to bring a pen.

I have finds on every day since July 16th, 2003. And FTFs on GC1AG09 and GC28FNK. I have not yet DNFed every calendar day (I have five days to go).

For those interested, I found a user with 2120 events attended, apparently on only 22 different events. That is kind of impressive in and of itself. http://www.geocaching.com/seek/nearest.asp...3c-a856a55b0874

The worst thing for me as a finder after I've solved a difficult puzzle is to have it be so difficult to find that I either DNF it or it's too hard to get to that I can't claim it. In either case, I don't get any reward for solving the difficult puzzle. I'd much rather claim a LPC for those caches. Sure I understand it's nice to have clever hides or nice long hikes, but I'd prefer to separate them from the tough puzzles. I do agree that hiding a LPC in a thematically appropriate location or with a thematically appropriate container can still make an otherwise ordinary hide more rewarding for a puzzle solver.

For me, it's a sport. I have won geocaching competitions, and it hasn't been accidental. Calling something that my entire life revolves around an "activity" just wouldn't make sense. For some people, softball is just an activity (and beer is involved). For others, it's a sport. I can live with that.

And as long as we're at it, this guy has already logged over 1200 caches in the past day (including Germany, U.S., Slovakia, and Australia).

We only take action on cache logs in limited situations such as profanity and personal attacks that violate the Terms of Use Agreement. Other than that, taking action on someone's cache page is out of bounds for us. I regret the burden this places on the affected cache owners. I might suggest that Groundspeak think a little further about this current policy. Fake find logs can affect real cachers. This cache, for example, would previously have appeared to many cachers (especially GSAK users) as questionable and possibly one to avoid wasting time on, based on the string of DNFs without a Find. Now, it shows up as recently found.

I saw one of these logs and didn't take offense at the time. I had actually run into this cacher at another cache that same day (where he did not mention the conference in his log), and he had told me he was on his way back from San Francisco (after I asked him where he was coming from), but he didn't tell me why he was in San Francisco. I thought it was nice when I read the log later that told me where he was, even if I wasn't interested enough to click the link. It would probably be hypocritical for me to complain about this kind of log anyway, as I tend to drop random things into my logs to try to keep them interesting, rather than just the boring "TFTC", but it would bother me perhaps to see the same message on a hundred caches in the same day.

Please, NO! The captcha added to waypoint downloads is icky. About 20% of the time, the thing is illegible. I'm going to start saving photos of the worst ones and see whether ANYBODY can figure them out.

Oh, it's a little interesting how I found out about this joker last night. So, I went out for an FTF on GC2FAJM last night. I put the cache on my watchlist, so that I would know whether somebody was logging the cache before I got to it (it had already been solved more than two hours earlier by three others). While I had the cache in hand and was signing the blank log, email arrived with PowerCachingLtd's log. Uh, I don't think so!

A lot of the puzzle caches logged in California belonged to candcfamily and cachbefound. I'm not sure that either of them are forum regulars. Two of my caches were logged, and I'm definitely not a forum regular. All the caches I saw logged seemed to be in the same area (as if the bot logged everything based on a Nearest search). Even though this account is gone, it looks like a new one has started up (attacking Hawaiian caches): JackBobBoy Maybe there are more coming? I should probably add a note to all my caches that any log with just the text "tftc" is subject to immediate deletion without verification.

Okay, I guess I just had to complain and it fixed itself.

Or is it just me? For the last hour, whenever I try to load a cache page, I get redirected to a 500 internal error page. 1. Go to http://coord.info/gc215n0 => get redirected to http://www.geocaching.com/error/error.aspx...he_details.aspx I'm on a T-Mobile Sidekick browser. I am able to load the home page.

The page refresh after selecting "Type of log:" is REALLY annoying. I select "Found it" and start typing my comment only to find that what I've been typing GETS ERASED!!! Yeesh.

Having this weird problem, which started last night and happened again tonight. 1. Load the cache page 2. Find the cache (I suck, so this takes me a while). 3. Click "Log your visit" => Get a message that says "You have been logged out." 4. Click "Log in" 5. Enter User name and password, check "Remember me" box, go back to password box and hit Return (since the button isn't appearing on the page still). => Get the message again that says "You have been logged out." (This pattern of step 4 and step 5 will continue.) If I go back to the cache page and reload, I can "Login to log your visit", but that gives me the same problem. However, if I just "Log in" from the cache page, I am able to log the visit (at least, I think that's how I finally got it to work).

Now that I've returned from two weeks of submitting logs on the road, I'd like to upgrade this to "really annoying". It's somewhat distressing to find that over half my logs now have typos because I couldn't see what I was typing. Sorry you're still having trouble. What's your browser? Cache URL (or is it all?), OS, screen resolution etc. This might be hard to repro. This is log.aspx I got a new phone. I no longer have this problem. The only problem I have now is that the "Submit log" button is way off the right edge of the screen for some unknown reason; so now I have to scroll for 2 1/2 seconds to get to it. Or sometimes I forget and accidentally hit the "Go" button which brings up the "Unpublished cache" page which really confused me for a few minutes the first time it happened. Also, I don't seem to be getting emails for logs I submit on caches that are on my watchlist. I'm not sure whether this is supposed to be a new feature, but I don't like it because I use the watchlist sometimes to verify that my log went through properly when the website times out on me (or I lose a cell connection), so that I know whether I need to resubmit my log.

Now that I've returned from two weeks of submitting logs on the road, I'd like to upgrade this to "really annoying". It's somewhat distressing to find that over half my logs now have typos because I couldn't see what I was typing.

I just tried it on the hide and seek page and got this as the result. By Waypoint - From Origin: N 37° 19.351 W 122° 03.195 http://www.geocaching.com/seek/nearest.asp...;submit8=Search its working fine for me Okay, the search page is better again. For some reason, all the options had vanished when I tried it earlier. I like that the navigational stuff isn't at the top anymore; so I don't have to scroll past it, but now lots of stuff seems to go off the right edge of the window. When I'm submitting a log, I can't even see what I'm typing half the time. That's kind of annoying.

how do I find a cache by waypoint id? also, search by coordinates seems to be broken for me. I entered "n 37 19.351 w 122 03.195" into the box and it returned me caches near "n 00 00.000 e 000 00.000"

For those of you who are streaking for a whole year, you'll want to put this cache on your must-do list: A Cache A Day ... for 365 Days? For me, today will be Day 1823 (if I can find one today); so I'm still shy of five years (Gitonyerhorse overestimated the length of my streak).

Okay, I guess I'll weigh in here. I had 17 DNFs on 4/29/07 (Ft. Worth, TX). I had 16 DNFs on 1/28/06 (Fresno, CA) and 12/25/05 (Ojai, CA). But, apparently I didn't accomplish the 20-20 that I referred to in this log.

DNF logs are usually more interesting reading that Found logs.