You shouldn't synchronize to Twitter. You (and Twitter) should
synchronize to the World Time Standard using NTP. It's a simple
process on Linux - you just install a package or two and read your
distro's system administration manual on how to configure it. It's
point and click on openSUSE
Yeah, well, that doesn't work very well for desktop apps ;-) Users would
go mad if you suddenly change their clocks.
Tom
On 9/6/10 10:22 PM, M. Edward (Ed) Borasky wrote:
You shouldn't synchronize to Twitter. You (and Twitter) should
synchronize to the World Time Standard using NTP. It's a
We have fixed a bug in our OAuth implementation that allowed timestamps in
the future to be accepted. We've now corrected this such that timetsamps
must be within a reasonable amount of time in cosideration to Twitter's
server clocks.
We return our current time in the Date HTTP header of every
This is true of all applications running to spec. We've always denied
requests that were behind our system clock by an unreasonable amont -- you
would be presented with this conundrum in that scenario as well, regardless
of our recent change to also apply this restriction to timestamps in the
Sorry for the trouble our alignment has caused.
Honestly, we should have announced we were going to harden this, but -- and
really we should have learned our lesson on this -- we were operating under
the assumption that OAuth clients develop to spec, which includes presenting
the current epoch
Peoples' desktops are almost all Windows (90%) or MacOS X (9%). I
don't know about Macs but I know for a fact that Windows XP and later
desktops can be *easily* syncronized to world time via NTP - in
fact, Microsoft has servers!
And for the 1% outliers like me (openSUSE 11.3) there are
