I am also getting this problem, despite it working perfectly yesterday. I've added a timestamp offset adjustment as you recommended just in case, and am sending an accurate GMT timestamp, but still getting 401 errors. There is no additional information included in the error, so I'm at a loss.
Was anything else changed? -- 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
