Shared publicly  - 
 
If you use Feedburner, better plan for something else...
7
14
Wendy S's profile photoAdam Tinworth's profile photoNeville Hobson's profile photoDavid Kutcher's profile photo
35 comments
 
Just FYI, but shutting down the API is not the same as shutting down the service.
 
+David Kutcher The service will remain - but with no API, no one will receive your blog posts through your feedburner RSS.

So, if a blog has 1000 RSS subscribers via feedburner on 19th October, they will have none on 20th October.

Equally, any services that people use to share your work with their followers via your feedburner RSS will cease to work.

The carrier here, is that it's possible Google will offer some kind of redirect - however, as Neville says in his post, there has been no word from Google regarding this.
 
+David Kutcher agree, David. Yet to all intents and purposes, the service does become shut down for most people who use it as a means to publish their content, ie, enable others to subscribe via RSS feed and email.

Basically, what +Jim Connolly said :)
 
I don't think this is right. It looks to me like the Awareness API and the FeedFlare API are being closed but that DOES NOT MEAN that Feedburner itself is closing. Which in turn does not mean that all the feedburner RSS/Atom will disappear. If you don't agree then come up with a cite because nothing on https://developers.google.com/feedburner/ says the feeds will disappear.

However, if I was relying on feedburner, I'd take this as a warning and switch either to an alternative service or to the native RSS of whatever platform I was using. Simply to avoid getting screwed at some stage in the future.
 
Hi +Jim Connolly that is not what that means at all. APIs are for 3rd party programmers, giving them the ability to take advantage of the service via their own software products. If your blog uses Feedburner as a service, which is what 99% of people do, this won't affect them at all. Your RSS feed, published by Feedburner, will not be affected.
 
I agree 100% with +Julian Bond 
"[...] if I was relying on feedburner, I'd take this as a warning and switch either to an alternative service or to the native RSS of whatever platform I was using. Simply to avoid getting screwed at some stage in the future."
 
Just saying there is a huge difference between shutting down the APIs and shutting down the service. If they were going to shut down FeedBurner I think it stands to reason that they'd be posting that message on the main FeedBurner page and on the page right above your feeds, not on the Developer pages.

I think it might behoove your readers if you added an addendum to your post ;)
 
+Julian Bond appreciate the information, Julian. It would really help if someone at Google would post, somewhere, a clear explanation  of exactly what shutting down the API actually means to Feedburner users. A lay explanation, something very clearly understandable by anyone. If not Google, a credible explanation from someone. That would be great.
 
Joining the discussion here - after raising the same issue as +David Kutcher over on the original post. Closing an API is not the same thing as closing the service. The Feedburner APIs did very little other than give you a way of pulling your Feedburner subscription stats into other metrics systems. The death of the API will kill a few WordPress plugins and some app, but not much else. The core business of serving feeds and providing metrics on them is not dependent on the APIs, and those services are unlikely to go away as long as Google sees value in serving ads through feeds. Given where Google makes the majority of its money, I suspect that day will be a long time coming. 

A more positive read of this would be that they're sweeping away the deprecated (and, I suspect, ill-used) APIs prior to the final integration of Feedburner into the rest of Google. 

However, positive or negative, their communication has been terrible. 
 
Just to follow up, while doing some research around the subject, I noted this in the CV of +steve olechowski Feedburner co-founder:
"-Led integration of FeedBurner into Google AdSense product line"

Which goes at least some way to confirming that serving/measuring feeds for ad-serving purposes is core to what Feedburner is now. 
 
+Adam Tinworth I hear that view from a few folk, Adam. I guess that is what Feedburner has evolved into. Yet most people I know have used Feedburner for years as a distribution channel. If the API is shut down next month, RSS feeds will no longer work, right? Metrics and all that may still, but that's not what many people see Feedburner as, ie, a metrics service - it's about content distribution. That's how I see it, too.

I really wish someone from Google would clearly explain what's going on.

AlI I see right now are loads of opinions from people (including me), most of it conflicting.
 
+Neville Hobson No, RSS feeds should work absolutely fine after the API is shut down. They do not require or use the API. Google has to re-serve the feeds to be able to provide metrics on them. That's the whole purpose of using Feedburner. WordPress, and before it Movable Type et al, have always been capable of serving feeds natively. 
 
+Neville Hobson unfortunately I can see what happened here: a development manager posted that update on the FeedBurner Developer site intended for developers that understood what they were talking about. When that post was picked up by non-developers it of course became confused.  I doubt any Google employee is going to post anything, mainly because to them (the development manager) they probably think they're being crystal clear. The API is being shut down with no mention of the service.
 
+Adam Tinworth ok, Adam, let's be crystal clear here.

You're saying that Google's planned shut down of the Feedburner APIs on Oct 20 will make no difference to RSS feed and email delivery that use Feedbun as the delivery mechanism? Everything will continue working as it does today?
 
To the best of my understand of what the Feedburner APIs do - that's exactly what I'm saying. 
 
exactly!

API = application programming interface, has to do with people who have programmed software that interfaces with their service, not with people that USE the service as you are.
 
+Adam Tinworth thank you for taking the time to add some much needed clarity. I really appreciate it.
 
BTW: The feedback here is a perfect example of the value of Google+ in particular and social networks in general!
 
+Jim Connolly Google+ is very good at making discussions easy to participate in - and easy to keep up with. If they every release a comments plugin for a blog, I'd be very tempted to switch. 
 
+Adam Tinworth And note here that G+ doesn't have RSS/Atom feeds. So you couldn't feed your list of G+ posts into Feedburner for onwards transmission.
Wendy S
 
(I'm not a developer so I'm a bit confused.  This thread has definitely has helped.  One more questions... will the "subscribe by email" function still work if the RSS is still working?  
 
There is a broader point here about FeedBurner and its value as a redistribution service. I expect it will continue after the API shuts down. However, Google has already closed the @Feedburner twitter account, already closed the Feedburner blog, and already abandoned the Feedburner.jp domain - including all its users. So while the service currently continues, what do these moves say about Google's commitment to it?
Wendy S
+
3
4
3
 
A public statement from Google would be nice right about now.
 
And yet,feedburner is still alive :-)
Add a comment...