Yay! Google is popularizing my preferred solution to leapsecond hell and making it easy for everyone to use/sync: https://cloudplatform.googleblog.com/2016/11/making-every-leap-second-count-with-our-new-public-NTP-servers.html …
-
-
-
Replying to @bofh453
.
@RichFelker seriously though, why does leap smear exist? Or any of this insanity. Just treat the it as a 1 second offset & step/slew it.1 reply 0 retweets 0 likes -
Replying to @bofh453 @RichFelker
it's a 1 second offset, the FLL will resynchronize in under 20 minutes when I tested it, for a slew.
1 reply 0 retweets 0 likes -
Replying to @bofh453
The idea is to smooth across 20 hours rather than 20 minutes for a more stable clock rate, I think.
1 reply 0 retweets 0 likes -
Replying to @RichFelker
who cares, it's a 1 second delta. anything needing more precision than that is already using TAI & their own atomic clocks.
1 reply 0 retweets 0 likes -
Replying to @bofh453
It allows matching/comparing timestamps across internet with precision exceeding network latency.
2 replies 0 retweets 0 likes
That doesn't work if every host is doing its own skew, possibly with different algorithms, to smooth out leap seconds.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.