Not sure what you're saying. Newsblur, feedly and theoldreader all have APIs already. So really the questions are:
1. How hard would it be to migrate from the GR API to any of those ones
2. Which ones is the better ecosystem to support.
From what I can see, Feedly is the least effort because they're duplicating the old API. However, their ecosystem sucks from a UX perspective (at least for those of us who want the old GR workflow). Theoldreader sounds good, but since there's no apps it's impossible to comment on their API and whether it's usable. Newsblur has an awesome UX, a couple of apps already, and is open source which implies that others may contribute and improve it too. So it gets my vote - if I had a choice.
But hey, the only person whose opinion is relevant here (from a Newsrob perspective) is Mariano, so until he decides whether to port to a new API, and if so which one, it's all rather academic. ;-)
Why not use one which already has an API?
--
You received this message because you are subscribed to the Google Groups "NewsRob User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to newsrob+u...@googlegroups.com.
To post to this group, send email to new...@googlegroups.com.
Visit this group at http://groups.google.com/group/newsrob?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
When I say better ecosystem, I mean from a user experience perspective - so look/feel, workflow, and compatibility (see earlier comment a about browser extensions).
I'm probably not going to get to this until it's too late, but the Reader information model looks like almost a proper subset of IMAP.
I'm tempted to just jam a feed->IMAP gateway onto a GMail account out of perversity, but a modded dovecot seems like it'd work.