On Tue, 25 May 2010 19:49:28 -0500
"Brian Smith" wrote:
> This is known and expected behavior. There have been other threads
> about it in the last couple of weeks. If you get a 401 response, you
> should compare the Date header of Twitter's response to the current
> system time. If it is signifi
I'll make this much clearer in the documentation, and also include
tips to work around it dynamically.
We have a revision of our OAuth implementation that we'll be gradually
introducing into the system in the near future. It's going to be
opt-in for awhile so that we can work out any kinks, as it'
This is known and expected behavior. There have been other threads about it
in the last couple of weeks. If you get a 401 response, you should compare
the Date header of Twitter's response to the current system time. If it is
significantly off then you should warn the user so they can fix it and/or
