I had a hard time balancing in yoga class this evening. I suspect that I was too hot or too dehydrated, or both. My mind kept going back to my typical, sinful, after-yoga Slurpee®. Some evening, I'm going to be good and walk across the street to the juice bar (or get back into the habit of going to QFC for a bottle of Bolthouse Farms™).

One of the most comfortable asanas for me remains Salamba Sarvangasana (Supported Shoulderstand). In class, though, we do a modified version that I've never been able to find an illustration of - with the back a lot more horizontal, and the tailbone resting on a block. We haven't done Salamba Sarvangasana in class in a long time, so coming in a close second for me is a pose we do quite often: Vrksasana (Tree Pose).

We did an advanced asana this evening, one that I'd never done before: Eka Pada Rajakapotasana (One-Legged King of the Pigeons Pose). We modified it with a strap between the raised foot and the hands. It was a tough one to hold (it is an advanced asana, after all), but I could see how comfortable it can be, once I get used to it. It gets my vote for the best English name, anyway.

As much fun as eavesdropping on people's public conversations is observing what people order at the cafeteria. At breakfast this morning, as I waited in line to pay for my veggie omelet, the guy in line ahead of me had this on his tray: two scrambled eggs, an order of hash brown potatoes, a side order of seasoned potato wedges, and a can of Pepsi.

That Travel Bug that I wrote about yesterday morning has shown up. Someone posted a note saying that they'd picked it up some time ago, but had been away from a computer and couldn't log their find. I'm very glad for this news - not only for the Travel Bug owner, but also for us. There are few feelings in the game/sport of geocaching worse than being the last one to find a cache before it got muggled - or being the last one to drop a Travel bug before it goes missing. (The fear is that you weren't quite stealthy enough and a muggle saw you uncover the geocache.)

Here's a blog that I think Phillip will enjoy: Mighty Optical Illusions. In order to visit the blog, I would recommend having either (a) a fast connection (b) patience or (c) both. (By the way, I spotted that hidden FedEx arrow a very long time ago.)

On April 2, we picked up a Travel Bug from a geocache a few blocks from home. The Travel Bug had been dropped into the geocache the day before, after traveling 696 miles from California. It had been launched in California on August 13, 2005, and had visited several California geocaches before landing in the geocache a few blocks from our apartment. On April 8, we dropped the Travel Bug into a geocache in Magnuson Park. As we started walking back to our car, I realized that I had forgotten to take a photograph of the Travel Bug in the park, to post in the Travel Bug's log. I considered going back to retrieve it, but instead I took a photograph of Lake Washington, near the cache location. I felt kind of bad about being lazy - I like posting photos of Travel Bugs, so that its owner can see it on its travels.

On April 19, a geocacher found the Magnuson Park cache, and commented that someone must have picked up the Travel Bug. On April 23 and 30, two more geocachers found the cache, but didn't mention the Travel Bug. Yesterday, the Magnuson Park cache was found by our favorite finder of Travel Bugs, who commented that the Travel Bug has definitely gone missing.

That poor Travel Bug. It made its way up the west coast, and on its debut in Washington, we pick it up, keep it less than a week, drop it off without a photograph of its journey, and it disappears.

During a second, and a third, login, our computer connected to the internet quickly and error-free, without the need to click "Retry." I think Phillip said it best: "Tech Support hates intermittent problems."

(Phillip had called our ISP when the problem first showed up on Friday, while I was at yoga class. He tells me that the support person tried her best to help, spending a half hour on the problem, but in the end could only suggest re-booting the computer - which appeared to solve the problem, but didn't.)

So far, the problem seems to have fixed itself. Phillip's theory is that our computer overheated. My theory is that it was a temporary problem with one of our ISP's servers. We may never know.

All this weekend, it's taken us about four error messages to get one successful connection to the internet. This morning, it connected right away (and, I noticed, a lot fast than it has been doing). Right now, I'm calling this morning a fluke, but I'll see. I'm guessing that the problem is with our ISP's software, which may have gotten messed up slightly during an upgrade. That's my guess, since the modem seems to be working OK. As frustrating as I find computers, I admit that I do enjoy trying to solve the problems.

Phillip and I returned to church yesterday because it was our turn to do Coffee Hour (with Eric & Jamie).

After church, Phillip and I went to the U District. We did some window shopping before we watched V For Vendetta at The Varsity. We both enjoyed the movie very much. It was thought provoking, and we talked about it on our drive home.

When we got home, I watched the DVD of Peter Jackson's King Kong. I enjoyed it, but I'm not enthusiastic about it. I've read negative reviews about the movie's three hour length, but I liked it for the epic scale of the storytelling. The digital effects were impressive, but it left me with a few comments. There was one scene, in which Ann Darrow was entertaining Kong with her Vaudeville routine, when I suddenly became aware that the actress was filmed against a "real" background - which made me wonder what was off about the digital backgrounds used previously. Also: I'm starting to wish that, along with the advances to make computer-rendered surfaces look real, the same care would be taken to obey the laws of physics. (If I were jerked around the way Ann was, I'd be a quadriplegic - if not dead.) And how about showing computer-rendered scenes from a somewhat believable camera angle?

So here's my idea for a more realistic computer effect: Include the "camera" in the shot. Instead of impossible sweeps through space while showing Kong on top of the Empire State building, include a part of a biplane in the foreground, and make the shot a little jumpy - as if the "camera" were mounted on a biplane. Limit the range of the "camera" movement, as if the "camera" were on a crane or helicopter.