loverfishy

Count me as another person in favor of reverting to the old email notification format. I find the new one to be awkward, and full of useless (and broken) HTML and images. Plain text was much better, and easier on both my desktop computer and mobile device (faster to load, less data, more concise). I don't complain often, but seriously thinking about turning off all controllable notifications.

Caching today in Minnesota- T4 (had to cross a frozen marsh)- fortunately, the cache was VERY winter-friendly:

Woohoo!!! Opened my mail today, and received a lovely surprise from dawsoncity- I particularly loved the very neat handmade card with the inuksuk on it! Thank you, stay warm, and Merry Christmas! (Sent you an email through your gc profile as well to let you know it arrived.) 1. Participating Date - 3 November, 2013 2. Received Name Date - 15 November, 2013 3. Mission Complete Date - 29 November, 2013 4. Mission Received Date - 17 December, 2013

I ended up DNF'ing the cache, but the location was awesome, and I think the cache is under several inches of ice (not the ice behind me in the pic). Minnesotans aren't afraid of a little winter!

I did not participate in this event, but know some people who did: http://www.geocaching.com/geocache/GC4D9Z1_mt-elbert-flash-mob A 5/5 flash mob event that involved getting to the summit of Mt. Elbert, a 14er in Colorado, AND learning choreography. Given the 10-mile roundtrip hike to the top of the 2nd highest peak in the continental US in a certain timeframe AND having to learn dance moves, I think that definitely merits a higher difficulty than 1!

1. Participating Date - 3 November, 2013 2. Received Name Date - 15 November, 2013 3. Mission Complete Date - 29 November, 2013 4. Mission Received Date

Well, I've almost been hit by a deer while biking to a cache (bolted out in front of me), and seen numerous others as well as a few moose. Wild turkeys are very prevalent around here, so I've seen large fleets of those while caching; same with squirrel, chipmunk, rabbits, frogs, and garter snakes. I also had an incident where I almost reached into an active paper wasps nest while trying to grab the second stage of the multi- fortunately, my most memorable "wildlife" encounter happened shortly before that, so I had wised up and used my phone cam to take a pic before I stuck my hand into the tree hollow. Behold, I give you the memorable Felis domesticus aka kitty cat: http://www.geocaching.com/seek/log.aspx?LUID=adb7fdd6-3824-4e6f-b892-2b0d76180670

Got my name- trackable should be here in a couple of days, and then I will send it off! 1. Participating Date - 3 November, 2013 2. Received Name Date - 15 November, 2013 3. Mission Complete Date 4. Mission Received Date loverfishy

Another shed-sized one that I found on my tour from MN-WA and back: http://www.geocaching.com/geocache/GC37K21_ammo-can-super-size-it

Looking forward to this! 1. Participating Date - 3 November, 2013 2. Received Name Date 3. Mission Complete Date 4. Mission Received Date

I had a puzzle cache that was PMO, mainly because it was a bit tricky with a few red herrings thrown in, and I wanted to limit it to more experienced cachers to avoid a lot of frustration on the part of novice cachers (and it had a theme which was probably attractive to kids). It also had better-than-normal starting swag, which I was hoping would be fairly traded. I recently converted it to non-PMO, as I had intended to do right from the start after a few people had found it- I had checked the cache before I switched it, and the swag trades were more than fair- cache was actually better stocked at the time of the switch than it was on initial placement. I thought the audit log was interesting in that it let me know as a cache owner who might be trying to solve the puzzle, but on the same token, I can see where it might limit people from trying to solve a puzzle- might make a few people self-conscious if they knew the owner could see the several dozen times it took to view the cache page before solving it. For me, the information is interesting, but not necessary. I don't really see the need for it, other than curiousity's sake. For those whose argument is that it will help to track a cache thief, etc., I don't really see that will help. If someone was truly interested in destroying or pilfering a cache and then trying to monitor a reaction, there are better ways of doing it- GSAK or putting a cache on one's watchlist rather than visiting the page itself. Also, just because someone has an interest doesn't prove that they have malicious intent, or that they were even anywhere near a location. My overall opinion: abolish the audit log