Specifically, the 2010s were 99% complete as of exactly 11:31:12 UTC on Monday 25 November 2019
Show this thread
-
-
-
Cripes I forgot to take leap seconds into account, despite having specifically created a JavaScript library so that I could easily take leap seconds into account in cases like this https://twitter.com/sortiecat/status/1200146005930446848 … https://github.com/qntm/t-a-i
Show this thread -
There were three leap seconds this decade and there isn't one scheduled for 31 December, which means the actual 99% point was thirty milliseconds earlier, at 11:31:11.970 UTC
Show this thread -
> const tai = require('t-a-i') > const start = tai.unixToAtomic(Date.UTC(2010, 0, 1)) > const end = tai.unixToAtomic(Date.UTC(2020, 0, 1)) > new Date(tai.atomicToUnix(start + (end - start) * .99)) 2019-11-25T11:31:11.970Zhttps://github.com/qntm/t-a-i
Show this thread -
-
-
Leap seconds are only announced six months in advance. We don't know how long the 2020s are going to be
Show this thread -
Specifically, leap seconds (or lack thereof) are announced in IERS Bulletin C, which is charmingly addressed "To authorities responsible for the measurement and distribution of time"pic.twitter.com/Qn7FoJbLSX
Show this thread
End of conversation
New conversation -
-
-
it turns into a barber pole progress bar at midnight December 31
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.