On Fri, Jun 11, 2010 at 11:16 AM, Vassil Dichev <[email protected]> wrote:
> > The public feed is already available via twitter api ( > > statuses/public_timeline.json) without authorization > > Yes, that's intentional, but even statuses/public_timeline.xml cannot > be parsed by a feed reader... > > If we keep the same HTTP authentication setup, it will just work if we > this might be a problem when twitter shifts to OAuth (think this happens in July?) > use the twitter API convention to use the extension to determine the > type of the response, e.g. public_timeline.rss, public_timemline.atom, > etc. > Good idea
