Vetoing FeedBurner

I’ve been a fan of FeedBurner for a long time. Going all the way back to the early days at b5media when they were a good company. Then they sold out to Google, and I warned any who would listen exactly who they would become. It was denied, though (most likely in good faith), and then they went down hill. Since the Google acquisition, they have slowly ported over to Google servers and infrastructure – an enhancement that was supposed to help. I can honestly not say if it has or it hasn’t. What I do know is that they are not noticeably better.

Then, of course, they had an outage today.

I’d call that the equivalent of calling out sick on the third day of a new job.

In the next 30 days, I have decided to remove all of my content from FeedBurner. They no longer have my vote of confidence, nor do I trust their competence. It’s probably a management thing more than technical. Much of the same team is still in place as was prior to the Google acquisition. You know, when they were good.

Please ensure that, if you subscribe to this feed using a feed reader (You really should use a feed reader… it does make blog reading so much easier. Despite my clear disdain for Google in this matter, I swear by Google Reader), you are subscribed to


For the time, this URL redirects to FeedBurner, but it will soon not and you don’t want to lose the feed subscription.

For a very long time, we have needed a viable alternative to FeedBurner. I don’t think we need all the bling that FeedBurner offered necessarily. But we do need an alternative to FeedBurner that will take a feed, normalize it for the most feed readers, provide some insight around readership (such as number of subscribers) and an extensible framework/API for using and publishing that data.

I’d very much like to talk to anyone who is developing options around this concept.