[twitter-dev] Re: 401 unauthorized
Sorry, what hack is that? I've heard a bunch of advice on working around this, but nothing conclusive. I believe he means changing from https://api.twitter.com to http://api.twitter.com. I can confirm that this works for me as well. Obviously not ideal, but an interim solution? -- 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
[twitter-dev] OAuth authorizing multiple accounts and disabling automatic redirection when account is already authorized
That's a long subject line, but I haven't seen much related to it (there was one post last Autumn but didn't seem to have any resolutions. I'm working on an app where an app user may want to authorize multiple Twitter accounts. Right now if they are already logged into Twitter (say, with their primary account) and the account is already authorized, they don't even get the option to sign in to a different account; the OAuth flow just redirects the browser immediately to the callback URL. Is there any way around this? Is there some way to pass a username on the GET or in the headers? Thanks, Nick
