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....
Regards, Karthik On Sep 2, 2:07 am, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > 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 minutes -- with the intention to rectify this > more gradually in the future. > > In the meantime, we strongly suggest clients perform a timestamp sanity > check. I'll work on formalizing and abstracting the few options developers > have to make this smooth. > > Some day we'll finally release our improved OAuth 1.0A implementation that > will also be very specific with you about the drift detected in your > timestamp. > > Thanks, > Taylor > > On Wed, Sep 1, 2010 at 1:55 PM, M. Edward (Ed) Borasky < > > zn...@borasky-research.net> 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. > > > Then again, I used to work at Goddard Space Flight Center - I was spoiled > > by having clocks accurate to a microsecond available as wall plugs. ;-) > > > -- > > M. Edward (Ed) Borasky > >http://borasky-research.nethttp://twitter.com/znmeb > > > "A mathematician is a device for turning coffee into theorems." - Paul > > Erdos > > > Quoting Tom van der Woerdt <i...@tvdw.eu>: > > > 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 least my old LG ENV and current Verizon Droid > >>> Incredible tell me what time it is. ;-) > > >> -- > >> 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 > > > -- > > 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 -- 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
