The public feed is already available via twitter api ( statuses/public_timeline.json) without authorization
D. On Fri, Jun 4, 2010 at 2:17 PM, Richard Hirsch <[email protected]>wrote: > On Fri, Jun 4, 2010 at 2:06 PM, Vassil Dichev <[email protected]> wrote: > > I've been thinking for some time about some type of RSS/Atom feed (not > > only for the public timeline), because this is one of the few ways you > > can track which messages have already been read (apart from the mail > > action, but it has a different usage scenario). So adding a feed for > > e.g. all API methods that Twitter supports wouldn't be much more > > effort than just for the public timeline. Of course, the feeds would > > need authorization when necessary. > > Thought about that as well. Was considering having Public feed without > authorization and personal feeds with authorization. What I don't know > is what RSS readers can deal with authorization > > > > > Vassil > > > > > > On Fri, Jun 4, 2010 at 1:37 PM, Richard Hirsch <[email protected]> > wrote: > >> I've been looking recently at various integration technologies and > >> thought RSS might be one option for the public timeline. What about > >> having a configuration setting, that a customer could decide whether > >> it is active or not. > >> > >> We could probably re-use existing API code. > >> > >> D. > >> > > >
