"How "the people" install a law, if not by voting for congressmen and let them install it?"
Huh? Creating laws is a power given to government by the Constitution, so it doesn't fall under the 10th Amendment. As an example of how this works, the Federal government has no Constitutional power to set building codes, so that's a power which the states have. Having said that, the Feds do sometimes get involved with State powers, by doing things like withholding funds if the states don't follow Federal will (such as building roads to Federal standards). But the Feds have no power to _force_ the states to follow Federal standards.
As another example, the people have a right to privacy, if for no other reason than the Feds have no (or very limited) power to violate such a right. There were big debates about even adding the Bill of Rights (the first 10 Amendments) to the US Constitution, the argument against being that if the Feds had no Constitutional power (for example, to legislate firearms), then there should be no need to explicitly guarantee a right to arms. Also, if some rights were spelled out, the Feds would act as if those were the only ones which existed. That's supposed to be covered by the 9th Amendment ("The enumeration in the Constitution, of certain rights, shall not be construed to deny or disparage others retained by the people."), which is in practice completely ignored by the Feds.
It can be difficult to explain unless you've lived here for a time, because the US isn't really a nation of law, but of power. The Feds have the power to control "Interstate Commerce," which was meant to prevent states from doing things like charging tariffs (tax) to other states when goods were shipped through a state. But the Feds got a Federal court to say that growing crops in a garden for your own use or birds flying between states is "Interstate Commerce," so they make laws which are unconstitutional to anyone with common sense. Our "law" has no clothes, but no one will say it. So there can be a big difference between what we're promised by our Constitution, and what actually happens.
But most people don't care. Panem et circenses, they have TV to watch.
Standard timezones were introduced as a practical convenience, so people in close proximity could share common (standard) time, as opposed to every town having their own 12:00 high noon. But, the timezone itself was still locked naturally to Sol, only the borders were artificial/political. Similarly, the leap second allows clocks worldwide to tick simultaneously based on an artificial human definition of the second, which was previously 1/86400 of a solar day. Leap seconds exist because the second itself is now an artificial construct, and they're needed to stay in sync with nature.
Biggest problem is that there can't be anything but 86400 seconds in a POSIX day _and_ it enumerates time as seconds since 1/1/70, two things which are mutually exclusive. "Right" time fixes some things, but can break stuff which expects POSIX time.
But yes, ntpd (the reference implementation) is very broken - it doesn't even follow its own RFC with regard to enumerating time. Of course, anyone who is inclined to produce a correct implementation will bump into the fact that the reference implementation is spewing incorrect timestamps everywhere, and systems expect that. It was developed to keep POSIX time, so just like POSIX, doesn't deal well with leap seconds or UTC.
No, you're very wrong. "The people" is a term of art widely used in the Constitution, and refers to residents/citizens. When the 1st A says "...the right of the people peaceably to assemble..." do you seriously claim that it refers to Congress?
"daylight savings time doesn't inject any new time, it just retreads old time/skips time."
It doesn't even do that, it just switches between timescales. 3:59 EST = 4:49 EDT. The only thing the government mandated change does is define when the switch occurs. Informally, when someone states the time or sets their clock, they don't consider the xST/xDT part, so the change forward/backward appears to be a 1 hour change. DST doesn't make time discontinuous nor make in non-monotonic.
Leap seconds aren't "artificial," any more than standard time zones are. They're directly related to the earth's natural rotation, as timekeeping has been for millennia. They are to the earth's rotation as leap days are to the earth's orbit. Additionally, time is monotonic, with or without leap seconds (or DST, for that matter, which merely involves a switch to a different timescale).
The biggest source of problems is POSIX, which some design-by-committee decided should define a day as having a fixed length, ignoring the existence leap seconds.
If you don't care about second accurate time, you don't have to deal with leap seconds, and your complexity problem is solved.
A powerpoint presentation is not a "paper." He publishes the leap-seconds.list file, which doesn't meet its own definition, which states "The first column shows an epoch as a number of seconds since 1 January 1900, 00:00:00". It doesn't do that, as it doesn't include leap seconds in that count (in a leap seconds file!!!). When asked about that error, he made the "leap seconds are forgotten" claim, which is ludicrous. He doesn't understand them, so wants to get rid of them because he doesn't understand how to deal with them.
Yet amazingly, Judah Levine doesn't understand how leap seconds work! He has claimed "In the legal definition of UTC, a leap second is 'forgotten' once it happens." Uh, what? There is no such "legal definition," and the normative definition, from the ITU-R, not only says no such thing, but provides a method for enumerating leap seconds.
Here you go: US 10th Amendment. Unfortunately, that's only how it says it works. In practice, the federal government does whatever the fuck it can get away with.
Perhaps said Google employee should focus on Google, which tends to be clueless about a lot of things. If you install a private CA cert, your Android phone will then start lying to you, claiming "This network may be monitored by an unknown party." (or similar). Nope. I who they are, I deliberately installed the cert, and your incorrect message only makes me tend to ignore any warnings you give in the future. OTOH, it also comes pre-loaded with a shitload of enabled CA Certs, most of which I likely have no use for, and which Google expects me to simply accept as trustworthy. WTF is "Government Root Certification Authority?" certainly sound like someone I wouldn't want to trust. Anyone remember Diginotar?
AFAIK, that's not to change the long term frequency, but to allow more phase noise. If you can provide an authoritative reference which says otherwise, please do.
Good luck with battery power. I assume, since he's asking about wireless protocols, he wants a battery powered wall clock. If it could be wired, there would be no need for wireless, he could just get a PoE clock.
Slashdot Mirror
So it's true what they say - Aspie kids can't recognize sarcasm.
Lazy people, and those who never learned to tie their shoes will be ever grateful!
Why didn't she just get an iPhone? The government has openly admitted that they're so secure that even they can't crack them.
"How "the people" install a law, if not by voting for congressmen and let them install it?"
Huh? Creating laws is a power given to government by the Constitution, so it doesn't fall under the 10th Amendment. As an example of how this works, the Federal government has no Constitutional power to set building codes, so that's a power which the states have. Having said that, the Feds do sometimes get involved with State powers, by doing things like withholding funds if the states don't follow Federal will (such as building roads to Federal standards). But the Feds have no power to _force_ the states to follow Federal standards.
As another example, the people have a right to privacy, if for no other reason than the Feds have no (or very limited) power to violate such a right. There were big debates about even adding the Bill of Rights (the first 10 Amendments) to the US Constitution, the argument against being that if the Feds had no Constitutional power (for example, to legislate firearms), then there should be no need to explicitly guarantee a right to arms. Also, if some rights were spelled out, the Feds would act as if those were the only ones which existed. That's supposed to be covered by the 9th Amendment ("The enumeration in the Constitution, of certain rights, shall not be construed to deny or disparage others retained by the people."), which is in practice completely ignored by the Feds.
It can be difficult to explain unless you've lived here for a time, because the US isn't really a nation of law, but of power. The Feds have the power to control "Interstate Commerce," which was meant to prevent states from doing things like charging tariffs (tax) to other states when goods were shipped through a state. But the Feds got a Federal court to say that growing crops in a garden for your own use or birds flying between states is "Interstate Commerce," so they make laws which are unconstitutional to anyone with common sense. Our "law" has no clothes, but no one will say it. So there can be a big difference between what we're promised by our Constitution, and what actually happens.
But most people don't care. Panem et circenses, they have TV to watch.
Standard timezones were introduced as a practical convenience, so people in close proximity could share common (standard) time, as opposed to every town having their own 12:00 high noon. But, the timezone itself was still locked naturally to Sol, only the borders were artificial/political. Similarly, the leap second allows clocks worldwide to tick simultaneously based on an artificial human definition of the second, which was previously 1/86400 of a solar day. Leap seconds exist because the second itself is now an artificial construct, and they're needed to stay in sync with nature.
Biggest problem is that there can't be anything but 86400 seconds in a POSIX day _and_ it enumerates time as seconds since 1/1/70, two things which are mutually exclusive. "Right" time fixes some things, but can break stuff which expects POSIX time.
But yes, ntpd (the reference implementation) is very broken - it doesn't even follow its own RFC with regard to enumerating time. Of course, anyone who is inclined to produce a correct implementation will bump into the fact that the reference implementation is spewing incorrect timestamps everywhere, and systems expect that. It was developed to keep POSIX time, so just like POSIX, doesn't deal well with leap seconds or UTC.
No, you're very wrong. "The people" is a term of art widely used in the Constitution, and refers to residents/citizens. When the 1st A says "...the right of the people peaceably to assemble..." do you seriously claim that it refers to Congress?
"daylight savings time doesn't inject any new time, it just retreads old time/skips time."
It doesn't even do that, it just switches between timescales. 3:59 EST = 4:49 EDT. The only thing the government mandated change does is define when the switch occurs. Informally, when someone states the time or sets their clock, they don't consider the xST/xDT part, so the change forward/backward appears to be a 1 hour change. DST doesn't make time discontinuous nor make in non-monotonic.
Leap seconds aren't "artificial," any more than standard time zones are. They're directly related to the earth's natural rotation, as timekeeping has been for millennia. They are to the earth's rotation as leap days are to the earth's orbit. Additionally, time is monotonic, with or without leap seconds (or DST, for that matter, which merely involves a switch to a different timescale).
The biggest source of problems is POSIX, which some design-by-committee decided should define a day as having a fixed length, ignoring the existence leap seconds.
If you don't care about second accurate time, you don't have to deal with leap seconds, and your complexity problem is solved.
A powerpoint presentation is not a "paper." He publishes the leap-seconds.list file, which doesn't meet its own definition, which states "The first column shows an epoch as a number of seconds since 1 January 1900, 00:00:00". It doesn't do that, as it doesn't include leap seconds in that count (in a leap seconds file!!!). When asked about that error, he made the "leap seconds are forgotten" claim, which is ludicrous. He doesn't understand them, so wants to get rid of them because he doesn't understand how to deal with them.
Yet amazingly, Judah Levine doesn't understand how leap seconds work! He has claimed "In the legal definition of UTC, a leap second is 'forgotten' once it happens." Uh, what? There is no such "legal definition," and the normative definition, from the ITU-R, not only says no such thing, but provides a method for enumerating leap seconds.
Here you go: US 10th Amendment. Unfortunately, that's only how it says it works. In practice, the federal government does whatever the fuck it can get away with.
"Even if the DOJ has the best lawyers on the planet - how would you ever measure it? "
It's often done by drawing a line on the ground, then seeing which party can stand on the line and send a stream of urine farther.
The Netherlands scans one billion tulips!
"It's time to redistribute the dirt!"
They're trying. Haven't you watched any of the debates?
The only role federal government can play here legally is to put out the wild fires using helicopters and airplanes."
I must have missed the part where they were given those powers when I read the Constitution.
Perhaps said Google employee should focus on Google, which tends to be clueless about a lot of things. If you install a private CA cert, your Android phone will then start lying to you, claiming "This network may be monitored by an unknown party." (or similar). Nope. I who they are, I deliberately installed the cert, and your incorrect message only makes me tend to ignore any warnings you give in the future. OTOH, it also comes pre-loaded with a shitload of enabled CA Certs, most of which I likely have no use for, and which Google expects me to simply accept as trustworthy. WTF is "Government Root Certification Authority?" certainly sound like someone I wouldn't want to trust. Anyone remember Diginotar?
"Know anyone who would pay for a 50% reduction in cancer risk? They should bottle that contamination"
So, homeopathic radiation? They'll make a fortune.
I have a Heisenberg clock. It always has the correct time, except when i look at it.
If you can point to one of the common "atomic" wall clocks which uses WWV, please do.
AFAIK, that's not to change the long term frequency, but to allow more phase noise. If you can provide an authoritative reference which says otherwise, please do.
Good luck with battery power. I assume, since he's asking about wireless protocols, he wants a battery powered wall clock. If it could be wired, there would be no need for wireless, he could just get a PoE clock.
"You implied the salesman knowingly sold an insecure system when you said he "should win salesman of the year".
I did no such thing. He should win it simply for selling a costly, high tech, high support solution in place of a wall switch.
Trump wants to wall off Mexico. I don't think HEY-ZEUS would choose him for anything.
You really should learn about broadcast domains and routers before displaying your ignorance.