They barely care about FeedBurner as it is. They've discontinued all of the advertising intergration, not updated the blog in any amount of time nor do you really get that much of the product itself. There's some pretty basic Google Analytics connection, but the main data we get out of it is download numbers for our podcast (http://76streetpod.com) and podcast network (http://76streetnetwork.com). It seems like every couple weeks the statistics stop for unexplained reasons only to have the Google group light up with nary an explanation. Along with mostly useless developer documentation for how the product outputs what it does or how it changes entries in a feed, FeedBurner is a useless hunk of crap that is almost certain to shutdown. An recent gripe is that when you use it as a feed proxy it doesn't pass along subscriber numbers like any other good feed parser, so a FeedBurner feed of a FeedBurner feed doesn't pass long info to the original FeedBurner feed or feed (but will pass along downloads, though it's only because FeedBurner is just a glorified Location header then.) I originally only went with FeedBurner over an open solution for expediency, but I've never liked giving Google more information on our users or giving up my control of our feeds to a product that has been limping along for years. It wouldn't take much effort to replicate FeedBurner. Maybe it's time I hunker down and do it. I've been planning for a FeedBurner switch since the beginning by using its "branded" feed feature and using a subdomain of ours for feed hosting. I hope everyone else has been wise enough to do so, as well, though looking at our network membership feeds, I know they haven't.