The shortest day was 31 January 1968. It ran for 86399.902592 seconds
-
-
Replying to @qntm
During 31 January 1968, UTC ran 3 millionths of a percent (0.002592 seconds) slower than TAI. But we removed 0.1 seconds from the end
1 reply 3 retweets 8 likes -
Replying to @qntm
Correction, I meant to say "TAI ran 3 millionths of a percent faster than UTC" above. Both times. Figures are correct though
2 replies 2 retweets 7 likes -
Replying to @qntm
Here is the code I used to work out those year lengths https://gist.github.com/ferno/d92f218ab51bcecdd1075fa1e1fd07b6 …
1 reply 0 retweets 8 likes -
Replying to @qntm
And here is the code for those day lengths https://gist.github.com/ferno/ecfcf88206f984a5fa8bcb73d6d505f9 …
1 reply 0 retweets 7 likes -
Replying to @qntm
For reference, a typical 24-hour day runs for 24*60*60 = 86400 seconds, and a typical 365-day year runs for 86400*365 = 31536000 seconds
2 replies 1 retweet 7 likes -
Replying to @qntm
The basic problem here is that the planet Earth is a terrible clock
2 replies 16 retweets 38 likes -
Replying to @qntm
It spins too slowly, it spins at irregular rates, it is constantly slowing down, and it can never be wound
6 replies 4 retweets 18 likes -
Replying to @qntm
Vibrating caesium atoms are much more reliable, and that's where we derive atomic time from
2 replies 4 retweets 10 likes -
Replying to @qntm
Unfortunately, for the purposes of civil timekeeping, the rotation of the Earth is all that matters, and nobody cares about caesium atoms
1 reply 11 retweets 26 likes
UTC is the compromise which gives us atomically accurate civil time while also actually tracking the solar day properly
-
-
Replying to @qntm
Be honest, you probably don't need to care about leap seconds
1 reply 0 retweets 16 likes -
Replying to @qntm
Anyway, the extra second at the end of 2016 is likely to be one of 2016's better seconds
2 replies 20 retweets 32 likes - 6 more replies
New conversation -
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.