Valid Blog Clients

Does anyone know of a good Blog client for Windows that actually writes out valid XHTML?  They all seem way too fond of tags that are verboten in XHTML Transitional, like the old italics and bold tags.  I'm playing with the "BlogThis!" client built into NewzCrawler now, which is the best I've found so far, but it's not perfect...

// Now playing: Gordon Lightfoot - Wreck of the Edmund Fitzgerald //

Sally Ride

Sally Ride We went to hear Sally Ride speak on campus last night, it was a good presentation, mostly about how astronauts view the earth from space, complete with slideshow.  It was a bit dumbed-down for all the non space geeks in the audience, the word "Orbiter" was never used, in favor of "Space Shuttle", for example.  She did take questions at the end of her speech, and I think I was the only one who asked a good one, since most of the other people asking questions were 10 years old. :) Here's what I asked (here with less stammering):  "There's been some discussion in the media recently about the future of the Hubble Telescope, and the administrations decision to not send future missions to service it due to the risk.  As someone who's served on both [the Challenger and Columbia] accident investigation boards, and as someone who has faced those risks herself, do you think the science being done by Hubble is worth the risk of human life to continue it?"

Dr. Ride's answer (not verbatim):  Yes, it's worth it.  The decision not to continue with Hubble is a bad decision, and the information that we're getting from it is well worth the risk.

Rare Virus

We had an instance of a rare virus on campus last night, only TrendMicro has a writeup about it yet, but I submitted a copy of it to Symantec, our antivirus vendor, and they've supplied me with beta defs to stop it. They're calling it W32.Gaobot.SN, and it lives in a file called msgfix.exe From what I could see, it attacks machines with weak or blank Administrator passwords, then attempts to spread to other machines on the network. It also listens on port 6667 for instructions from the creator of the worm, so that it may do his dastardly bidding. Cleanup is pretty easy, just stop the process, delete the file, and remove the registry entry that calls it when the machine starts. Hopefully Symantec will have a writeup about it soon...