We have some lingering bugs around where the wrong error is thrown in a few instances. Hope to have them tracked down and rectified as soon as we can.
Taylor On Fri, Sep 10, 2010 at 6:12 AM, ilmart <elmer.toren...@gmail.com> wrote: > Hi Tim, > > I ran into the same problem last week. To fix the problem I mashed > together a little app available at http://twitter2rss.com > This app lets you read your Twitter home tweets via RSS once more. > > No registration is required, all it takes is you to authorize the app > with Twitter (all explained on the site). You should be in business > within minutes. > > Hope this helps! > > Cheers, > ilmar > > On Sep 8, 3:03 am, Tim Haines <tmhai...@gmail.com> wrote: > > Hi guys, > > > > I haven't fully confirmed this is what's going on, but it appears an > account > > I use for doing only user/show calls, and ONLY via oauth is getting some > bad > > error messages. > > > > I think in this case the account has hit it's oauth rate limit, and a few > > more user/show calls have been attempted. The error message being > returned > > is a 401 and has a response body saying: "Basic authentication is not > > supported" when it should perhaps read "rate limit exceeded". > > > > Cheers, > > > > Tim. > > -- > 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
