Unless your system does not have access to the Internet, there is no
excuse for not synchronizing its clocks to the world-wide NTP server
pool. Zero - zip - zilch - nada - absolutely no excuse! Five minutes
leeway is not really acceptable.
--
M. Edward (Ed) Borasky
http://borasky-research.ne
Hi,
I would make sure that your system's clock is within about 5 minutes of
Twitter's. We return our current time in the "Date" HTTP header of every
response. One easy way to fixate an application's clock with our servers is
to issue a HTTP HEAD request to http://api.twitter.com/1/help/test.xml --
Hi guys,
Does anyone know what is wrong with my code? it always returns "Failed
to validate oauth signature and token" (it did return access token and
access access secret few day ago)
here is my code (I use Hammock/TweetSharp library)
private const string _consumerKey = "cKey";
private const st
