Previously...

Where's my password-manager? Each site I access wants me to create a username and password. Many didn't get the memo in 1998 and still insist on using something other than an email address as the username. Some take it even further and want me to set up a secret question/answer to use as a password for recovering my password. How am I supposed to manage this information? Across multiple computers? When organizations like dreamhost occasionally leak my password info? Is OpenID going to save us?

Hey cool new web2.0 app, I don't want to give you my facebook/del.icio.us/flickr/gmail/bank password just because you promise you'll entertain me with a pretty redraw of the data. I might consider granting you temporary read-only access to one of these services, but, oops, nobody's invented that yet. I might even grant you full access, but I don't want to give you my password to do so. Otherwise, how am I going to remove you when you (inevitably) do something stupid like alter my data or spam my friends? Didn't kerberos figure all this out like last century?

Hey webapp, where's my data? I want to move my facebook profile to linkedin. How? You're telling me I need to download all my email/documents/pictures/contacts to my computer to move them from gmail/flickr/blogger to yahoo/shutterfly/typepad? Ok ok, I'd never move to typepad, but still, you get the idea: I used to have this computer, it had a "desktop" metaphor, and through that metaphor I could "copy" files, or use "save-as" to save Word docs as Wordperfect. I tell you, it was all space-age stuff back then.

So I check my inbox mail on my treo and never see spam. The greybox I can check once a week. Any mail that lands in the greybox and I later file gets automatically added to the whitelist. I don't have to worry about mail from people I know being tagged as spam because the senders are all in my whitelist. All is well, right?

Unfortunately, no. People change email addresses a lot more than I would have thought. If someone switches from yahoo to gmail, they're off the whitelist and suddenly my spam filter (which I've configured to be as paranoid as HAL 9000) gets to decide whether I see it. Uh oh.

So if I haven't yet responded to your email, well, now you know why. Sorry...

The Westminster Web site hopes to match last year's 125 million hits from more than 125 million countries. And once again, the Empire State Building will be lit in purple and yellow to highlight the show.

Wrong wrong wrong. Hits are indivisible, integer-like, one-to-one things. No way that X hits can come from more than X places. And what's with these 125 million countries? Must've come from the Eastern Bloc countries splitting apart. And all New Yorkers know that the Empire State is always lit with white light, and they just photoshop the color in later. Duh.

Also, if I could figure out why dreamhost's mail servers only run my spam filter on some incoming mail (not even that much of it), then I'd be a happier person.

Joel Spolsky, the grandaddy of 'em all (for me at least). I read his blog back before I knew what a blog was. Lately he seems to have jumped the shark over the wasabi thing, but we'll see if he can rally.

Damien Katz took the blog world by storm when he wrote about his work on the forumula engine for Lotus Notes. Now he's writing about his new project, CouchDb. My only complaint: I still don't know what CouchDb is. Damien, please, point me toward the explanation for people who can program but know nothing about modern web development!

Steve Yegge is the guy who made me realize Joel was jumping the shark. Steve recently did some popular stuff about agile programming and Google's dev process, but my favorite stuff is from his blog-rants. His Perl rant... I stumbled across it (following links from ongoing, probably) after I'd spent a summer hacking up a client-server cross-platform Perl thingy. The software worked and yet I felt guilty about inflicting a system written entirely in Perl on my employer. Steve's rant helped me realize where the pain was coming from.

Anyhow, some links and a vague reference to a future blog resurgence. That's all's I got for you. See you in January (hopefully sooner though - I just don't want to set the bar too high).