I've been giving some thought to all the things about Radio that bug me. Not that I'm anxious to replace it, of course, unless the thing I was replacing it with was just that much nicer.  [The .NET Guy]

Not that I'm all that anxious either, but here's an example.  Last night I was working on a long (for me) post and accidentally clicked a link on the editing page.  Bang, gone.  Can't figure out how to get it back, and I just lost my motivation for finishing it.  This sort of thing is the thing that frustrates me about browser based apps.  In a Windows app, if you fat finger ctrl+F4, you've usually got an escape route.  In a browser, another app decides whether or not you get a chance to back out of a data loss situation.  Browser based apps are nifty until this sort of thing happens to you a few times.  I like them for situations when I'm not at my normal machine, but I don't want to live and die by the browser.  Simon's Word Radio updater could be one solution, except that I don't use Word at home; Star Office works fine, thanks.  But Simon's provided Windows developers with a good base to start from, or you could write to the Blogger API directly if you must.  Am I interested?  Somewhat, I just have a day job to think about and a baby on the way in the next 8 weeks...

I don't see a pressing need to replace the server side, Userland's problems aside, because I'm not tied to their servers; I can always upstream somewhere else.  Maybe there's something happening on the server side that I'd lose if I abandoned Userland, I don't know.