The MS blog entry points at a Dev document about how it works, and that says this:
Known issues:
Some frameworks are known to calculate time incorrectly after a leap second occurs. For example, the.NET Framework uses its own internal logic to determine what time it is. Its logic does not account for leap seconds. So after a leap second is introduced to the Operating System the output of "System.DateTime.Now.ToString()" will be ahead by one second of the local system time. (We are working with the.NET framework team on this.)
Combine that with the many many steps on how to configure Win10 makes this sound like a really interesting new feature.
I already have a family archive of scanned tintypes of greatgreatgreat grandparents, photos, videos, and other ancestral artifacts that would fill 1% of that disc. So I think compression is going to happen.
Whatever is stored will need a whole lot of uncompressed material as examples of the sorts of things on the medium, and as a stepping stone to reading the on-media documents that explain how to decode any compressed materials, and even those compressed files should have copious amounts of uncompressed metadata.
The tweets by Scott Helme at https://twitter.com/Scott_Helm... show Chrome with uBlock Origin, but what are the other extensions and which tool is being used to show the infected sites?
"Ah, yes, Anacweon. I have just come from theah. Most bahbawous planet."
... and the analysis afterwards by Salvor Hardin...
Hardin continued: "It isn't just you. It's the whole Galaxy. Pirenne heard Lord Dorwin's idea of scientific research. Lord Dorwin thought the way to be a good archaeologist was to read all the books on the subject – written by men who were dead for centuries. He thought that the way to solve archaeological puzzles was to weigh the opposing authorities. And Pirenne listened and made no objections. Don't you see that there's something wrong with that?"
Penalties are aiming in the wrong direction because leaks will continue to happen.
Better to change finance law so that the victim is presumed innocent until proven guilty. A victim should not be penalized. Rather, the lender who fails to perform due diligence and verify identity before extending credit should lose. That would be a powerful motivation for the finance industry to adopt new techniques that minimize their risk of losing.
originally my login here was @10u8 until that stopped letting me login because suddenly the slashdot id became an e-mail address and the new code would not tolerate my old id
The first proposal to abandon leap seconds was presented to the ITU-R in 2004, and subsequent versions have been rejected for over a decade. It is evident that the usual process of ITU-R decisions is not capable of coming to agreement on the subject of leap seconds. It remains to be seen whether they will produce a new framework for studies which can produce an agreement in 8 years.
At the beginning of the graph, about 1963, the length of day is 86400.0013 SI seconds.
At the end of the graph, about 2015, the length of day is 86400.0010 SI seconds.
That is a shorter day, a faster rotation, an acceleration.
The ITU-R first received this issue as Question 236/7 in year 2001. They have spent nearly 15 years coming up with this list of 6 methods for dealing with leap seconds. In that note the most recent "Method D" from a group of countries who prefer no change because they are not satisfied with the documents that have been submitted to the ITU-R during the past decade.
The debate continues because it is not a technical issue. We know how to count SI seconds by physicists watching cesium atoms, and we know how to count calendar days by astronomers watching the earth rotate. The question is about time producers and time consumers -- which of the time producers will have the hegemony, and whether the time consumers have enough agency to choose what time scale to use for their applications. The question is whether the days of the civil calendar will remain related to the rotating earth, or change to be 794 243 384 928 000 hyperfine oscillations of cesium-133.
Please look at this tzdist internet draft which is close to becoming an RFC. The tzdist protocol can communicate the list of leap seconds along with the list of time zones.
Been there, did that, in the US from about 1957, the US and UK starting in 1960, and internationally from 1961 until 1972. The authorities in charge of the distribution of time utterly rejected that in favor of leap seconds. Then they went on a world tour getting agencies and governments to officially adopt UTC with leap seconds as the perfect time scale for all purposes.
The designers of GPS system time did understand. GPS system time is *about* 19 seconds behind TAI, not exactly 19, and the difference varies by nanoseconds. Perhaps nanoseconds is unimportant to some, but for others nanoseconds is very important. That makes them not the same, so choosing a separate name and offset avoided any confusion that they were the same. Think of it like a trademark issue; there are many kinds of cola, but TAI is a name for the original cola, and only BIPM is authorized to make cola with the name TAI.
Take another look at Method D, which was just added in March: "No change to the Radio Regulations as the results of the studies are inconclusive." This is one group of delegations going on official record saying that all the effort expended by the ITU-R over the past 15 years has been worthless for making any decision to change the definition of UTC. That is serious disagreement.
The ITU-R has outlined 4 methods for the future of UTC. Methods A1, A2, B, C1, C2, and D are from various delegations of the international assembly, and they are in serious disagreement with each other.
Slashdot Mirror
The MS blog entry points at a Dev document about how it works, and that says this: .NET Framework uses its own internal logic to determine what time it is. Its logic does not account for leap seconds. So after a leap second is introduced to the Operating System the output of "System.DateTime.Now.ToString()" will be ahead by one second of the local system time. (We are working with the .NET framework team on this.)
Known issues: Some frameworks are known to calculate time incorrectly after a leap second occurs. For example, the
Combine that with the many many steps on how to configure Win10 makes this sound like a really interesting new feature.
They're not insects. They're called Body Thetans.
It wasn't exactly for this reason that my great grandfather kept a shotgun loaded with rock salt, but I think it would work here, too.
I already have a family archive of scanned tintypes of greatgreatgreat grandparents, photos, videos, and other ancestral artifacts that would fill 1% of that disc. So I think compression is going to happen.
Whatever is stored will need a whole lot of uncompressed material as examples of the sorts of things on the medium, and as a stepping stone to reading the on-media documents that explain how to decode any compressed materials, and even those compressed files should have copious amounts of uncompressed metadata.
I predict this will be the response after reading followup studies on ocean health.
The tweets by Scott Helme at https://twitter.com/Scott_Helm... show Chrome with uBlock Origin, but what are the other extensions and which tool is being used to show the infected sites?
and dumping spacecraft there risks angering the Great Old Ones
"Ah, yes, Anacweon. I have just come from theah. Most bahbawous planet." ...
... and the analysis afterwards by Salvor Hardin
Hardin continued: "It isn't just you. It's the whole Galaxy. Pirenne heard Lord Dorwin's idea of scientific research. Lord Dorwin thought the way to be a good archaeologist was to read all the books on the subject – written by men who were dead for centuries. He thought that the way to solve archaeological puzzles was to weigh the opposing authorities. And Pirenne listened and made no objections. Don't you see that there's something wrong with that?"
Asimov answered the headline question with "no".
Penalties are aiming in the wrong direction because leaks will continue to happen. Better to change finance law so that the victim is presumed innocent until proven guilty. A victim should not be penalized. Rather, the lender who fails to perform due diligence and verify identity before extending credit should lose. That would be a powerful motivation for the finance industry to adopt new techniques that minimize their risk of losing.
The headline writer is in the wrong time zone.
originally my login here was @10u8 until that stopped letting me login because suddenly the slashdot id became an e-mail address and the new code would not tolerate my old id
ffmpeg has had the vid.stab filter for several years. The only news here seems to be another cloud service.
and that makes it good enough for me. LLAP
time to re-read Red Mars
The first proposal to abandon leap seconds was presented to the ITU-R in 2004, and subsequent versions have been rejected for over a decade. It is evident that the usual process of ITU-R decisions is not capable of coming to agreement on the subject of leap seconds. It remains to be seen whether they will produce a new framework for studies which can produce an agreement in 8 years.
I wish we lived in a world where regulators paid attention to astronomers. Astronomers were the ones who warned that implementing leap seconds was a bad idea (see the section "Coordinated Time" starting on page 345). Nobody listened to astronomers then, and astronomers have not gained such powers in the ensuing 45 years.
At the beginning of the graph, about 1963, the length of day is 86400.0013 SI seconds.
At the end of the graph, about 2015, the length of day is 86400.0010 SI seconds.
That is a shorter day, a faster rotation, an acceleration.
Please note that wikimedia chart shows the rotation of the earth has accelerated, not decelerated.
The ITU-R first received this issue as Question 236/7 in year 2001. They have spent nearly 15 years coming up with this list of 6 methods for dealing with leap seconds. In that note the most recent "Method D" from a group of countries who prefer no change because they are not satisfied with the documents that have been submitted to the ITU-R during the past decade.
The debate continues because it is not a technical issue. We know how to count SI seconds by physicists watching cesium atoms, and we know how to count calendar days by astronomers watching the earth rotate. The question is about time producers and time consumers -- which of the time producers will have the hegemony, and whether the time consumers have enough agency to choose what time scale to use for their applications. The question is whether the days of the civil calendar will remain related to the rotating earth, or change to be 794 243 384 928 000 hyperfine oscillations of cesium-133.
Please look at this tzdist internet draft which is close to becoming an RFC. The tzdist protocol can communicate the list of leap seconds along with the list of time zones.
Been there, did that, in the US from about 1957, the US and UK starting in 1960, and internationally from 1961 until 1972. The authorities in charge of the distribution of time utterly rejected that in favor of leap seconds. Then they went on a world tour getting agencies and governments to officially adopt UTC with leap seconds as the perfect time scale for all purposes.
The designers of GPS system time did understand. GPS system time is *about* 19 seconds behind TAI, not exactly 19, and the difference varies by nanoseconds. Perhaps nanoseconds is unimportant to some, but for others nanoseconds is very important. That makes them not the same, so choosing a separate name and offset avoided any confusion that they were the same. Think of it like a trademark issue; there are many kinds of cola, but TAI is a name for the original cola, and only BIPM is authorized to make cola with the name TAI.
Take another look at Method D, which was just added in March: "No change to the Radio Regulations as the results of the studies are inconclusive." This is one group of delegations going on official record saying that all the effort expended by the ITU-R over the past 15 years has been worthless for making any decision to change the definition of UTC. That is serious disagreement.
The ITU-R has outlined 4 methods for the future of UTC. Methods A1, A2, B, C1, C2, and D are from various delegations of the international assembly, and they are in serious disagreement with each other.