markandsandy

Just when I thought there was one less of them to DNF . We'll see you all at 9:00

What would be ETA back at the trailhead afterward? I mean, if we start early enough, some of us could go to Issaquah afterward, instead of before.... That depends entirely on the turnback point. Mom can take the entire loop which we ultimately want to do, but I can't speak for LandRover's Mom. I'll put it to you this way, if you feel you need to forage ahead to grab the caches and/or turn back early, our feelings won't be hurt. It still counts as an HOTM. Trail conditions I was going to post yesterday were going to be favorable, but I'm afraid part of it now may be worse than what was provided to me. (Mom rode her horse through there Monday morning before the storm.) Most of the trail is groomed but there are parts that become mucky when wet. I guess I was hinting that if we started a tad earlier, say at 9 am (the usual time), it might dovetail better with the other event, since a few folks wanted to do both. Selfishly, I was hoping to do the HOTM with friends as a birthday treat, then meet avroair at his event, but sounds like coordinating the two isn't in the cards. C'est la vie, it's your hike with your mom! I'll share birthday cake with the 1yo in Issaquah. Tasty! This discussion isn't over yet. Stay tuned. An earlier time would not be a problem for us, even though we have such a long way to go to get there.

It's really sad when you have to stop and think for a moment to remember how old you are. Both of us 51-60 group.

For those doing the hike, I highly recommend you take the WASL: 8th Grade Science Retake. I'm not saying the final is anywhere near to Moss Lake, but if my calculations are correct...

Create a bookmark list of your DNFs. When you view your bookmarks, there is a button to create a pocket query. Any new DNFs that you add to the bookmark will automatically be included the next time you run that query.

There have been requests before for the ability to do a query based on cache owner, or keywords. It would be nice. But for this case there appears to be a public bookmark of the caches that you can create a PQ from: State Park Wildlife Safari

Same here. Sent a test message through my profile and it came through, but those from my trackables and items on my watchlist have not.

This one is practically in our backyard, so we plan to join you. Neither mom will be with us, however. Hopefully we will be able to keep up with your mom.

The other thread is for closed roads, this is for opened roads. Don't you understand the difference? Seriously, they probably could be combined.

Ours is one of those names that people THINK they understand, but they are WRONG. My wife and I cache as a team, but our names are not mark and sandy. No immediate family members with those names either. It all started with a coat. My wife works for a company that is a wholesale manufacturer and supplier of clothing. She bought me a coat for hiking that had a defect, but it had the name Mark embroidered on it. She started joking about me being her boyfriend 'Mark'. The Sandy part came about when a Starbucks employee mis-introduced my wife as 'Sandy'. Since they already knew about my 'Mark' alias, we became Mark and Sandy. Now when we go in for coffee, they sometimes call us by our real names, and sometimes as Mark and Sandy. It really confuses the new employees.

Vinny is the result of a clinical trial gone bad.

As much as I want to climb the Monkey Tripod (I haven't climbed a tower like that since the 60's), I'm going to have to pass as I have other commitments. Have to do it some other day. Have fun everybody, and DON'T LOOK DOWN!

I'll admit, I did this numerous times in the years BC (Before Caching). The easiest car I had to get into was a '74 Pinto stationwagon. The windows by the rear seat were hinged at the front, with a latch at the back. You could pop the hinges out of the frame and open the window. Unfortunately, the last time I did this I didn't get the hinges reseated properly, and several weeks later they decided to pop out by themselves - on the freeway at 55MPH. Since the window was still attached by the latch, it didn't just fall off, it exploded - little pieces of glass everywhere. Sounded like a shotgun blast right behind my head. I haven't locked them into my truck yet. Partly because I have gotten into the habit of always checking (multiple times) where the keys are before closing the door, and usually have them in my hand just to be sure, even if I'm not locking the door. Also the truck beeps when I open the door and the keys are in the ignition. First time in the FRONT seat...

Thanks, kind of what I thought. I will be grabbing mostly stuff that I drive to anyway. I'm not planning any 3 or 4 mile hikes to a cache and if I was I wouldn't have dipped those. I was just wondering if there was an unwritten rule, like within 100 yards or a 1/2 mile or something. I'm strict concerning travelers so I'll only log a bug that I can at least wave over the top of an open container. Logging a bug for being in the proximity starts pushing the boundaries of virtual logging. My one exception to what BlueDeuce said is I will log my truck into an event, even if I can't wave it over the top of the building , but it does have to make it to the parking lot.

A Found It log isn't a point of honor, it's a statement of fact. Either you Found It, or (in this case) Did Not Find it.

From the cache listing requirements: Since you would not be able to show that you actually had someone who would maintain the cache, it probably would not even be published.

Actually, you can be an "FTF Hound" and have no FTF's. If you are a slow hound.

The solution is not to turn them into Traditionals, but if the ALR was the only reason they are a 'Mystery', removing the ALR changes the listing to reflect what they actually are. The difference that I see between this and the changing the cache type examples that you mention, lies in the 'once you have changed the wording to remove the ALR altogether or change it into an optional simple task' part of statement by MissJenn. If that is all you are doing, then changing it to its real type will more accurately reflect a cacher's history, it will now show what they really found. If I shoot a wolf in sheeps clothing, it's still a wolf. If the cache is actually changed, making the type truly different than it was, i.e. a Multi into a Traditional, or vice versa, I would think the appropraite thing to do would be to archive and resubmit and the previous finders histories are still correct, and future finders histories are correct.

Your doing something better than the people that make barcode reading software then. I sent the pics to three companies. None could read it. They told me it looks like a mix of two types of barcodes. What software were you using? Since it was pointed out later in the thread that the OT is asking whether or not to have the reviewer ask the owner to prove it's solvable, I won't give any details about my approach here. If my approach doesn't break down, and if I do complete the task, and the owner verifies my solution, I will post that it is solvable. But as someone else pointed out, just because nobody has actually found it doesn't mean that nobody has solved it. I also have a backlog of solved puzzles that I haven't found yet. As far as the original topic: It's rated a 5 star difficulty, so it's not expected to be any easy solution. If you can't solve it, then you can't solve it. The owner doesn't have to prove anything to you.

Oh boy, a birthday hike (for me)! Who's bringing the cake? Don't know about that, but clearly, a cache must be placed. I can see it now. An ammo can painted to look like a cake .

Vinny will become a reviewer.

I don't have time to spend completely solving it, but in just a few minutes time I identified which barcode type it was, and the part I have read makes sense. My bet is that by the end of the day someone in this thread will have a solution.

That's pretty much it (others will chime in, hopefully, with other hints and tips). You'll need to choose coordinates for your unpublished cache that don't conflict with possible future caches. Otherwise, when someone goes to publish their own, real, cache, the reviewer could see your unpublished cache as a conflict in terms of the minimum-distance-between-caches guideline. Maybe the middle of a big lake near you. I have three published caches of my own, so I just used the coordinates of one of my actual caches. That should avoid any potential conflicts. --Larry There's one more step you can do, and that is to archive the cache listing as well. You will still be able to access it, but that eliminates the coordinate conflict issue.