Check out NTP and your servers NTPD i think NTPD -q will show if your
server[s] clock is correctly regarding clock/timestamp.
On Oct 22, 2010, at 8:22 AM, CWorster wrote:
Maybe it's an issue with the clock/timestamp on your production
system.
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/b1faa40fb795a147/62183a53c25bd453
--
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
