oauth_timestamp (your oauth library probably does that) is also a timestamp. Verify that your server's time is right. If possible, sync via ntp.
Tom Sent from my iPhone On Jan 5, 2011, at 11:35 PM, cootcraig <[email protected]> wrote: > >> There are no known issues with timestamps. What is the timestamp you are >> sending to us? > > I'm not aware I'm sending a timestamp. I thought the whole request > was > get http://api.twitter.com/1/favorites.json?include_entities=1&page=1 > >> >> If your timestamp isn't close to the time of our servers (GMT) we will throw >> this error. >> >> Best, >> @themattharris >> Developer Advocate, Twitterhttp://twitter.com/themattharris >> >> On Wed, Jan 5, 2011 at 1:15 PM, cootcraig <[email protected]> wrote: > > -- > 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 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
