Hi... I'm slowly making my way through the OAuth landscape of twitter and I ran into a very odd inconsistency.
I registered my application and kept getting 401 HTTP errors (Unauthorized) using the Ruby OAuth library. If I access my application details via: http://dev.twitter.com/apps/edit/12341234 Compared with accessing it via: http://twitter.com/apps/edit/12341234 There's one checkbox that doesn't appear on the dev version: "Yes, use Twitter for login" After checking this, I was then able to get OAuth going. Is this deliberate? Or just an omission? Is this a sign that the Twitter API is going to prevent logins? How does that work with OAuth then? Cheers, Jason -- 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
