Live Writer works great with Community Server, but if you're like me you'll write a post, read it in Live Writer a couple of times and click "Publish." Then you'll read the post online and say, 'Dang it to Heck!' after seeing fresh errors and you're back in Live Writer for the fix(es). A couple more read-throughs, another "Publish" or two, and you finally get it right. The problem, despite the love you showed the post, Community Server is going to squeeze out that first crappy published version onto your feed. This isn't an issue unique to Community Server, and newsreader clients handle post versions differently, but here's what I've been doing to insure that my RSS subscribers read the same post that ultimately ends up on my site.
Instead of publishing, I first use the Live Writer "Post Draft to Weblog" option (in the "Save Draft" dropdown.) Then I'll go to my blog Control Panel and select to read the post from the "All Posts" listing. I make my edits back in Live Writer as usual (posting back as a draft) and then when I finally get it right I can click the "Publish" button in Live Writer with confidence. It's important to me that you guys who subscribe to my blog actually see the best I can deliver, not what is essentially a draft version. So now when you read a DBVT.COM post in your newsreader and think, "that's pure crap!" you can rest assured that the final version is pure crap, too.