Hi Taylor, We have users reporting that https://twitter.com/oauth/authorize?<oauth params> just returns an empty response (324 in chrome net:: ERR_EMPTY_RESPONSE), so it seems like it's timing out. Obviously, this never makes it back to our callback, so what should we do as an application in this case?
David -- 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
