How the Government Shutdown Warps Time Itself

Why don&#x27;t they use the Canadian National Research Council bulletin?<p><a href="http:&#x2F;&#x2F;time5.nrc.ca&#x2F;timefreq&#x2F;bulletin_tf-b.html" rel="nofollow">http:&#x2F;&#x2F;time5.nrc.ca&#x2F;timefreq&#x2F;bulletin_tf-b.html</a><p>In Canada if a budget isn&#x27;t passed it triggers an election. We don&#x27;t have government shutdowns.

Such an informative post; thanks for sharing this!<p>Also, and somewhat sad and just plain crazy: some functions of NIST are not considered essential!?! It seems to me someone in the gov. is not clearly reporting who and what functions are truly essential to the higher ups in the gov. Then again, maybe they have, but the higher ups ignore them. <i>sigh</i><p>Nevertheless, cool post.

*could possibly affect an edge case of utc leap second distribution if Another shutdown happens during a leap second year (this is not one), AND lasts over 6 months. I get that it acks the clickbaity title at the beginning, but that coy bs doesnt help.

&gt; <i>Because TAI is not based on the Earth’s rotation, it’s not ever-so-slowly changing. It’s the measure of time against which UTC’s watch is occasionally correct. That correction is called a leap second: a 61st second that is sometimes added to particular minutes in UTC, like the very last minute of December 31, 2016. As of January 2019 there have been 27 such leap seconds inserted.</i><p>This seems backwards. Perhaps I&#x27;m misunderstanding what the author is trying to say, and another poster could help clarify?<p>If UTC is based on the earth&#x27;s rotation and TAI is based on cesium-atomic timekeeping, and UTC is slowing down, and TAI is &quot;the measure of time against which UTC&#x27;s watch is occasionally corrected,&quot; then how can UTC have leap seconds? Delaying for an additional second on December 31st would only make it one second <i>even slower</i>, exacerbating the problem.<p>I don&#x27;t see how adding a delay to the slower clock is going to put it in sync with the faster one.<p>Is it instead that UTC is TAI, plus leap seconds to slow it down to keep it in sync with the rotation of the Earth?

The license stuff seems weird without further context: even if they can&#x27;t copy that file, what&#x27;s the hold up to just &quot;encode&quot; the information from the bulletin on their own and putting it into their file?

We still can&#x27;t migrate to the metric system. Let&#x27;s work on that first!

So if I am reading this right people who use NTP aren&#x27;t affected. Is that right or does OpenNTPD depends on tzdata ?

Leap seconds are the most stupidest thing ever. It&#x27;s time to abandon UTC and start using what professional astronomers use: UT1

In my opinion it&#x27;s possible the Democrats will cave. The strategic situation is that Democrats care about the country, and Trump does not. However, not enough Americans are convinced of the latter fact. Once they are, the only rational decision is to cave - and then remove him from office as quickly as possible.

I have to wonder, if something like VLC can exist, which blatantly flies in the face of copywright law unchallenged, why do so many open-source projects get ridiculously anal about license issues? The problem here appears to be that the license (CC-BY 4.0) is only specified in the README file, not in the timezone data file itself. Like, do they really think that it only applies to the README, and if they use the data they&#x27;re going to get sued? I get that it&#x27;s important to cover one&#x27;s ass, but if it gets to the point where software breaks as a result, it&#x27;s gone much too far.<p>I wonder if the right solution here is to have some kind of body provide insurance against frivolous litigation over licensing issues for open-source projects, so that this kind of stupidity doesn&#x27;t arise.<p>Edit: It appears I was mistaken about the legal status of VLC: it is about software patent licenses, not software copywright licenses.