As long as you are requesting from the correct end point: http://api.twitter.com/1/statuses/public_timeline.xml (or .json) without any authentication credentials, this should continue working for you.
If it isn't, could you provide HTTP traces of your entire connection sequence, complete with the URL you are executing, all HTTP headers sent and received? Thanks, Taylor On Tue, Aug 31, 2010 at 10:52 AM, David "Markus" Hasselberg < darkwingsabl...@gmail.com> wrote: > I have developed a webpage that reads from a public user_timeline. > Starting today, August 31st, i receive error 53 "Basic authentication > is not supported." I understand that OAuth is now used instead of HTTP > authentication, but public timelines should still not require any > authentication, correct? > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
