Personally, this could be a killer use of App.net. Blend social with RSS and get something like Pandora for newsfeeds. Not sure how hard it would be to pull an RSS feed and then push that into an App.net stream, blended with some meta data on content and a machine learning algorithm which enhanced your feeds by finding similar feeds that has a high correlative match to what you read most. Just sayin'
I'm working on an opensource implementation of the API here if anyone is interested in helping out :) <a href="https://github.com/devongovett/reader" rel="nofollow">https://github.com/devongovett/reader</a>
All I know is that I will be on whatever reeder supports. So basically whoever makes that thing is going to be deciding my fate. I hope they choose wisely.
Also, an implementation independent test suite would be nice...<p>I'm sure there are plenty of corner cases where all the new implementations might fall down, or make different decisions than are expected.
I'm the project lead for Vienna, the open source RSS client for the Mac. We support Google Reader, and we want to support this:<p><a href="https://github.com/ViennaRSS/vienna-rss/issues/160" rel="nofollow">https://github.com/ViennaRSS/vienna-rss/issues/160</a><p>If you're a Cocoa developer, feel free to jump right in. If you're going to implement the server side, shoot me a note @mstroeck (app.net preferred).
That's a good idea but I nevertheless think big clients (client reader + integrated access to server api) will win anyway because if you have to pay a client and then pay a subscription to a server to have access to an implementation of this API I don't think it will be very appealing. All the current model of 'small' clients was based on the fact that the access to Google's (non official) api was free. That part won't be replaced.
I just wrote something similar on an another site:<p>"For now, Google Reader was the standard.
Now that it isn't it anymore, I hope that it will get developed a nice API to sync feeds between decides, and that the major reader will implement it.
This way every application would be able to sync with every backend, without any problem. And if a backend close, you could easily switch to a different one by changing one line in the configuration."<p>I seriously hope that this will be true. What has got me stuck on Google Reader for now (beside the "it just works" interface) is that every major application synced with it. I don't really want this to happen again, only with a different company.
Here a link to Mr Avocado? He the former engineer who created Google reader project in the first place.This is Just a suggestion from a user. Maybe getting him on board would help a lot in your project?<p><a href="http://www.massless.org/?area=Projects" rel="nofollow">http://www.massless.org/?area=Projects</a>
Please, as an advice to general HN posters, please avoid posting marco.org links here on HN, because his sole intention is to sell his readers out more than focusing on writing. That's a fairly grande accusation, but it's justified.<p>Do you know why is he writing about Google Reader now? Go to your HN homepage right now, as of writing this comment, the Google reader announcement has about 1700 upvotes. Ouch, that's a lot of views for someone to let go of. Hence, if someone writes something that compliments this announcement, common sense tells me that they would get more page views.<p>There's nothing wrong in having ads on your blog/website, people do it all the time. What's wrong is trying to create an impression to your readers that your sole intention is to write quality content, while you care just about pageviews. Please, realize that marco.org is no different from Techcrunch!<p>Marco isn't innocent, if you've been following him closely. Also, I think it would help if you take a look at this page where he just blatantly sells us, his readers like some piece of junk commodity.
<a href="http://www.marco.org/sponsorship" rel="nofollow">http://www.marco.org/sponsorship</a>