magicbeans. nothing if not awkward.

This morning, logged into avocado from work, I noticed that things were sluggish. Checking in with top, I found that a spam-bot had found and was exploiting George's mt-comments script. I put a stop to it by removing the script, figuring it unnecessary since he hasn't updated his blog in the better part of a year anyway.

Work was another day of playing with world flags for an IBM project.

And after buying a new orange shirt, it was off to VP2, again, for dinner. Two appetizers and a small soup, but it still ended up costing more than I should be spending on meals right now. It's just that I don't have any dishes or silverware or pots and pans or anything at home.

My fortune stuck to the inside of the cookie when I pulled on it, and ripped, leaving me with 'will have a party.' the 'You' being left inside the cookie fragment. So someone will have a party. Hardly noteworthy. Or maybe it's trying to warn me off of having my own party. That a housewarming 'all the way' up in Inwood will only lead to disappointment on the scale of my birthday party when no one makes the trek.

As I said the other night, the A stops at West 4th, around the corner from VP2, and is terribly convenient. Except when it isn't. No uptown blue-line trains were running due to problems at Canal Street. 'Go downstairs and take the F, V, B, or D to your destination,' the voice on the PA was telling us. What if the orange-line doesn't go anywhere near your destination? I suppose if all else failed, I could take the 1/9 to 207th and walk a handful of blocks crosstown. It wouldn't be any worse than walking from the JMZ in Bushwick up to Moore Street, although making all local stops the 1/9 would take much longer to get up to Inwood. As it happened, the problem was fixed before too long, and the announcements had actually convinced quite a few of the people milling around the platform to take an alternate train so that when the A did come it wasn't even all that crowded.

When I got home I had voicemail from Daniel. Explaining the exact problem that I had experienced this morning. Did Movable Type repair itself? As it happened, it was the install on Alex's mushroom site. Again, since he's not using it, deleting the script was the simplest course of action.