Making this a real issue so it doesn't fall through the cracks...
According to @episod in https://dev.twitter.com/discussions/10889
"We had an issue over the weekend that required a hotfix to oauth/authenticate. This hotfix ended up requiring cookies where they were previously non-required. We are working on a follow-on fix today that will resolve the underlying issue without requiring cookies for environments such as yours that do not support them."
This is particularly frustrating, as parts of API 1.1 (i.e. home timeline for some users) are currently broken if cookies are enabled/sent.
Since this change was made, no one has been able to sign-in/authenticate with our apps.
Updates
- Resolved on April 9, 2013 - web clients without cookies support should be able to once again utilize the authentication sequence
