3 ms·

I don't understand why Dave objects to Feedburner in the "2a" point of his post. He seems to be saying that relying on Feedburner as a corporate API can or will

I don't understand why Dave objects to Feedburner in the "2a" point of his post. He seems to be saying that relying on Feedburner as a corporate API can or will burn you if Feedburner changes their policies. But Feedburner lets you serve your feeds off your own domain (e.g. feeds.mattcutts.com) using a CNAME in DNS. Here's an article from 2007 that talked about how Feedburner made that functionality free after Google bought Feedburner: http://www.mydigitallife.info/how-to-activate-and-use-feedburner-mybrand-for-free/ http://www.mydigitallife.info/how-to-activate-and-use-feedbu... So if Feedburner ever makes you angry or disappoints you, people are still coming to your domain to get the feeds, and you can just swap Feedburner out with a different system. As far as commercial APIs go, that seems pretty developer-friendly.

davewiner 14y ago
Of course you have to do that long before Google breaks your feed. I don't really object to Feedburner in this piece, btw, I just say people are going to regret it. In my opinion (clearly labeled as such). And of course this is your opinion (not so clearly labeled, esp since you work at Google, assuming you still do).
- Matt_Cutts 14y ago
  Yup, I still work at Google. I set up feeds.mattcutts.com years ago, and my hope is that anyone who cares enough to configure Feedburner in the first place would click around to find the MyBrand feature and set it up. I'm not trying to take away from your fundamental point about corporate APIs, by the way. At this point, any time I use a product/feature I'm thinking about how I would export my data. If the answer on data liberation isn't what I hoped, I often avoid that product.