[time-nuts] Leap second smear at Google

[Christopher Quarksnow]

Besides the famous Android stint described in Google bug 5485
https://code.google.com/p/android/issues/detail?id=5485 that took 2 years
to fix, so many Android phones system clocks were 15 seconds fast then, I
just found the source of another discrepancy where Google spreads the leap
second offset to avoid artifacts with servers, platforms, environments or
programs unable to handle a sudden second leap :
http://googleblog.blogspot.com/2011/09/time-technology-and-leaping-seconds.html

Maybe not as bad as Oracle in 2009 :
http://www.pcworld.com/article/156453/article.html

I don't know how "elegant" this solution from Google is, especially with
Google Wallet time payments or transactions that could be back-dated in
relation to a banking system, or other Google apps, but I thought it might
be of interest to some before they need a house of clocks to keep in sync
with Google on such days ! http://www.youtube.com/watch?v=xyRKQ84ztkE

Christopher Quarksnow