NewsGator 1.2 Released!
Update: Yeah. That didn't go real well. The post itself was fine, but the html sent up the pipe... in a word, ooof.
I'm fussy, as a preface. And I should also front-load the fact that Greg emailed me within like 38 seconds of my original post. So, not only is NewsGator my aggregator of choice, but you really can't quibble with Greg's attentiveness and support. My backend is from my own abusive hands that mirrors MT's api because it tends to get good tools support. I generally store content with as little html as possible and then systematically add certain kinds of things through different formatting accessors. Simplest example, I don't store html linebreaks and block formatting, just links and inline formatting really. When a html consumer wants the post, it calls the relevant formatter and then I strip in whatever I've configured for HTML linebreaks (e.g., <p/>). So I've got fussier needs than most users because of this and I also obsessively hate FONT tags and SPANs to nowhere and the like.
Which is all to say, I can post with the third-party plugin NewsGator leverages here, but at some point MSHTML is going to take control of what gets sent up the wire and I personally am probably not wild about what it's going to do. You're probably going to need to scrub any of this kind of output before folding it into an xhtml:body because the mshtml output is not exactly xhtmlicious.
Personally, I just want nice, clean, simple html, my templates and back-end take care of the complicated stuff (and MT does too).
---
If you use
NewsGator or haven't been stuck in a 24-hour meeting, you already know
Greg announced the release of 1.2 earlier. In fact, this post is more about me posting straight from NewsGator than it is about passing along any truly vital information. It's a little different than using w.bloggar, its basically like sending HTML email; the upside is you get a lot of bang for your buck by leveraging all the built-in Outlook editing functionality.
My only concern is learning to live without source-level editing--basically what I believe will happen, is Outlook is going to send a lot of old-school nasty HTML up the pipe. FONT tags out the wazoo. What I think I might do is tweak the server side to strip this out (as I dream of a non-interop version of tidy).
If
Marcelo ever releases a version that supports IBlogExtension, that'll pretty much be all I need to finally stop searching for optimal tools.