5 minutes (or even 15 minutes) for the OAuth timestamp is a major
problem on the iPad. This device doesn't have a guaranteed network
connection and therefore doesn't do NTP syncs on a regular basis. It's
common for these devices to be off by an hour or more.
We do a check at startup against the
But you don't need to ask the user to update their time at all, do you
Craig? You simply make a non-rate limited request to Twitter before making
any other requests, scrape the current time from the Date HTTP header
Twitter responds with, and then for as long as the application is active
you
Dear Taylor,
I am getting one new issue.
In my application , randomly some api's returns 401 - invalid
signature error...
I am not sure whether twitter server only returns 401 randomly or some
problem in my request..?
Most of the time my requests are working fine...
Please help me out
Dear Taylor,
I am getting one new issue.
In my application , randomly some api's returns 401 - invalid
signature error...
I am not sure whether twitter server only returns 401 randomly or some
problem in my request..?
Most of the time my requests are working fine...
Please help me out
Hey Karthik,
If some methods are returning 401 and others are succeeding it sounds
like your encoding could be going wrong. Can you share the calls which
401 and a couple that are successful so we can see what maybe
happening. It would be helpful to see the Auth header and signature
base string
Thanks you all ...Actually the problem with the API which I am
using to get the target mobile time.
The API always returns local time when I change it to GMT The
things are fine in target.
Thanks once again for this timely help on Time...
On Sep 2, 4:45 am, Andrew W. Donoho
Dear Taylor,
I still done get how to sync my mobile clock to the twitter server
clock.
Can you explain little more..?
On Sep 1, 9:34 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Karthik,
Make sure that the time on your device is in sync with Twitter's clocks.
We return
You mean I just issue a http request http://api.twitter.com/1/help/test.xml
to the server before I start my login..?
On Sep 1, 9:34 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Karthik,
Make sure that the time on your device is in sync with Twitter's clocks.
We return our
You'll need to:
a) determine the system time on the device you're running on
b) determine the system time with Twitter by reading the Date HTTP header
from a response to making a request to
http://api.twitter.com/1/help/text.xml
c) Convert both times to UTC-based epoch time in seconds.
d) If
I'd think mobiles - at least the common ones (iPhone, Android,
Symbian, Blackberry, Palm, etc.) would be synchronized to world time
automatically. At least my old LG ENV and current Verizon Droid
Incredible tell me what time it is. ;-)
--
M. Edward (Ed) Borasky
http://borasky-research.net
Not iOS (iPhone, iPod Touch, etc) - my iPod Touch seems to be 18 seconds
out of sync.
Tom
On 9/1/10 10:39 PM, M. Edward (Ed) Borasky wrote:
I'd think mobiles - at least the common ones (iPhone, Android, Symbian,
Blackberry, Palm, etc.) would be synchronized to world time
automatically. At
That's a surprise - I'd expect Apple to be on top of stuff like that!
Even so, 18 seconds is well within Twitter's outrageously generous
tolerance of five minutes.
Then again, I used to work at Goddard Space Flight Center - I was
spoiled by having clocks accurate to a microsecond available
Uh ... not counting solar flares and disrupted satellite
communications, of course ... 2012 / 2013 is supposedly going to be a
challenge ;-)
--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb
A mathematician is a device for turning coffee into theorems. - Paul
Our generous time range is actually +- ~ 15 minutes -- I just tell everyone
within 5 minutes to keep things proper and sane. :)
Understand that our correction here is a bit sudden; we may make a
compromise tweak that will restrict future timestamps, but now with a more
relaxed resolution than 15
On Sep 1, 2010, at 15:55 , M. Edward (Ed) Borasky wrote:
That's a surprise - I'd expect Apple to be on top of stuff like that! Even
so, 18 seconds is well within Twitter's outrageously generous tolerance of
five minutes.
There are different sync. points for different devices. For
15 matches
Mail list logo
