Meet the Guy Whose Software Keeps the World's Digital Clocks In Sync (ieee.org)

New submitter Wave723 quotes a story on IEEE: In many cases, the internal clock that ticks away in a laptop or desktop computer is synchronized to an official time service maintained by the U.S. National Institute of Standards and Technology (NIST). This free service shares Coordinated Universal Time with personal devices, web browsers, financial trading software and e-mail programs throughout the world. The service receives 150,000 requests per second (roughly 16 billion a day) from systems that repeatedly ask, 'What time is it?' "If you have a PC, it's probably synchronized to the time service," says Judah Levine, the man who originally built servers and programmed software to send time over the Internet for NIST back in 1993.

Comments

What time is it/

[Anonymous Coward]

It's time to stretch your anus

Re:What time is it/

[Anonymous Coward]

Yeah yeah, we know that joke. Stretch the asshole out to about six feet, give him a radar gun, and put him on the end of the bridge.

Very cute

Re:What time is it/

[Anonymous Coward]

Goatse Guy looks like the accountant next door compared to rosebudding...

Broom

[Anonymous Coward]

Not interested. Let's meet the guy who invented the broom.

Nut in charge of the nut house.

[msauve]

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.

Re:Nut in charge of the nut house.

[sexconker]

A leap second is really no different from a leap day or the "extra" or "lost" hour due to daylight saving time.
I don't know why people have such a problem with it.

Count your ticks, determine how to show the date and time for a given locale.

Re:Nut in charge of the nut house.

[Anonymous Coward]

Huh?

The Impact of Leap Seconds on Digital Time Services
Judah Levine
Time and Frequency Division
NIST, Boulder, Colorado
paper

Re:Nut in charge of the nut house.

[UnknownSoldier]

Because the leap second like DST are _artificial_ and adds unnecessary complexity to an otherwise brain-dead simple algorithm. Complexity == Bugs.

The only one who gives a fuck about leap seconds are scientists.

Stop over-engineering a simple concept. Time should be monotonic, and consistent. Not this one-off shenanigans.

Re:Nut in charge of the nut house.

[msauve]

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.

Re:Nut in charge of the nut house.

[Junta]

Actually, the leap day is quite different than daylight savings time.

Usually, February has 28 days, except when it has 29 days. This is like a leap second, where once in a great while, a minute has 61 seconds.

daylight savings time doesn't inject any new time, it just retreads old time/skips time.

Practically speaking, a leap second would have been easier to model like daylight savings time (repeat one of the 60 seconds usually found in a minute), except that would mean some portion of indicated time would be ambiguous. That would have been perhaps aggravating for a whole day (two '28ths' of february would be pretty ambiguous for real-world concerns), but for a second it seems a bit more trouble than it's worth for all time systems to understand that there can be 61 second minutes...

Re:Nut in charge of the nut house.

[Anonymous Coward]

He doesn't want to deal with them because in many cases time is best handled monotonically - ie, each second that passes simply counts as 1 second. For a variety of reasons slowing a clock to show the same :59 twice or slewing a clock so that :58, :59 :00 move slower, etc etc all cause lots of confusion. Simplest is to standardize on a time measurement that increases 1 unit per one second as an example, then if people want to format, and add confusion after the fact they can (DST, time zone, leap day, leap second etc). The underlying time measure just needs to move forward 1 unit of time at a time (an ordered sequence). This doesn't make him a nut.

Re:Nut in charge of the nut house.

[msauve]

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.

Re:Nut in charge of the nut house.

[Anonymous Coward]

Leap seconds are a correction between the way that humans measure time and how the Earth spins
If this is not done, then there will be a difference between recorded and observed time
Accept it, or change the definition of a second, frankly leap seconds are easier

Re:Nut in charge of the nut house.

[Anonymous Coward]

Monotonic, consistent times fail to meet human requirements, like times that match up with the solar day.

Re:Nut in charge of the nut house.

[msauve]

"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.

Re:Nut in charge of the nut house.

[amorsen]

Unfortunately, Unix and NTP treat leap seconds completely different from Daylight Saving. They actually mess with the real measured clock, slowing it down. This is just completely broken of course, suddenly seconds aren't one second long any more. This has lead to system crashes and all sorts of fun.

There are two solutions to this: Either the NTP guys get their heads out of their asses, or leap seconds are abolished.

Unix is mostly ready, there can be 62 seconds in a minute in C, so all you do is switch the timezone files to the "right" directory instead of the "posix" directory (on GNU systems at least). But that cannot be done until NTP works.

Re:Nut in charge of the nut house.

[tlhIngan]

Because the leap second like DST are _artificial_ and adds unnecessary complexity to an otherwise brain-dead simple algorithm. Complexity == Bugs.

The only one who gives a fuck about leap seconds are scientists.

Stop over-engineering a simple concept. Time should be monotonic, and consistent. Not this one-off shenanigans.

The problem is there is a lot of time.

You may remember GMT, nowadays known as UT (not to be confused with UTC). GMT is time based on the Earth's rotation - when the sun is directly overhead, it's noon. There are approximately 86,400 seconds in a day here, but the mean solar day varies because Earth's rotation is not uniform. UT1 is the most common form of this, which is what time is measured at the prime meridian.

UTC is time derived from the atomic clock. It closely approximates UT, but since Earth's rotation is erratic, to keep the UTC day closely aligned with the UT day, leap seconds are sometimes added to ensure the difference between the two times is under 0.9 seconds.

TAI is the time as told by atomic clocks. Here, a day is exactly 86,400 seconds and there is no such thing as leap seconds - this is purely a monotonic clock that ticks away.

The problem is, well, there are a lot of variables. UT is measured generally once a day and clocks set to its time. UTC is a close approximation and generally used as it's easier to obtain without having to have someone observe the Sun every day to calculate when noon is. TAI is just the atomic clock time.

Leap seconds are introduced to keep UTC and UT relatively close to each other. TAI is allowed to drift, and eventually you'll have noon at midnight.

Which you pick is up to your needs. Leap years were created so people in the Northern hemisphere wouldn't be celebrating summer in December as the calendar drifts away from Earth's position in its orbit..

Then there's TAI, which is the true atomic time

Re:Nut in charge of the nut house.

[Anonymous Coward]

The explanations in that file make it clear that the timestamps are given as NTP timestamps. Unix time and NTP do not count leap seconds. In Unix time and NTP, there are always exactly the same number of seconds from 23:59:30 to 00:00:30, whether a leap second was inserted between those times or not. The extra second is dealt with by stopping the clock for a second or running it slower so that it's back in sync with UTC after a few minutes. It would be a colossal misstatement to say that NTP timestamps represent seconds since a fixed point in time. This is acknowledged in the explanation that leap seconds shift the entire NTP timescale, including the epoch, by one second. NTP timestamps represent the number of seconds since the NTP epoch. The NTP epoch is not one point in time. It's as many non-leap seconds back in time as have occurred since 1990-01-01 00:00:00 UTC. It's off from that point in time by the number of leap seconds inserted since then.

Re:Nut in charge of the nut house.

[Anonymous Coward]

Correction: 1900, not 1990. The NTP epoch is not 1900-01-01 00:00:00 UTC, it is as many seconds back in time as non-leap seconds have occurred since 1900-01-01 00:00:00 UTC.

Re:Nut in charge of the nut house.

[msauve]

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.

Re:Nut in charge of the nut house.

[OrangeTide]

time zones are artificial, they reflect political borders. And nothing is more artificial than politics.

Re:Nut in charge of the nut house.

[OrangeTide]

Except I can accurately predict centuries in advance when February 29 occurs.
Leap seconds are added whenever measurements cause a committee at the UN non-governmental organization that oversees the standard (International Earth Rotation and Reference Systems Service) to schedule for a leap second to be inserted.

Re:Nut in charge of the nut house.

[msauve]

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.

Re:Nut in charge of the nut house.

[Anonymous Coward]

They actually are very difference from daylight saving time. Daylight saving time is an offset against UTC. Leap seconds actually change UTC. Another difference is a leap second is applied to all timezones at the same time, while a leap day is only applied relative to each time zone. You also have the issue that a leap day is a change to a date while a leap second is a change to a time. It's hard to tell the difference between two clocks being 1 second off and not knowing which one is correct, but it is very easy to tell when a clock is a day off.

Re:Nut in charge of the nut house.

[Anonymous Coward]

Except NTP does the exact opposite: It doesn't "count" leap seconds. It leaves the conversion between NTP timestamps (seconds since the NTP epoch) and UTC timestamps (seconds since the UTC epoch) to the application. Every time a leap second is added to UTC, NTP switches to a new NTP epoch: The NTP timestamp 2272061000 marks the point in time that was 2272061000 seconds after 1900-01-01 00:00:10 UTC, which was the NTP epoch at that timestamp. That timestamp was 2272061010 seconds after 1900-01-01 00:00:00 UTC, which one might naively but incorrectly consider the NTP epoch. Currently, the actual NTP epoch is 1990-01-01 00:00:36 UTC.

Re:Nut in charge of the nut house.

[Anonymous Coward]

Damnit, 1900, not 1990. I did it again.

Re:Nut in charge of the nut house.

[Anonymous Coward]

Timezones are artificial no matter the justification. If we are keeping time by the sun, driving 1 hour in either direction would cause the time to change, even if only by seconds or minutes. Instead, it doesn't change until you reach some magical boundary (and I'm not even talking about timezones that skirt around political borders, I'm talking about longitudinal hour markers). And it is magical because it is compressing all the other longitudes into just that one.

Re:Nut in charge of the nut house.

[johnslater]

Time itself is an illusion. Lunchtime doubly so.

I think I saw that in Reader's Digest.

Re:Nut in charge of the nut house.

[Anonymous Coward]

I like one of the ideas someone had when adding a leap second.
The second count in time_t stays the same one second longer.
But in struct timeval the tv_usec keeps counting beyond 999; till 1999.

Re:Nut in charge of the nut house.

[UnknownSoldier]

> Leap years were created so people in the Northern hemisphere wouldn't be celebrating summer in December as the calendar drifts away from Earth's position in its orbit..

First World Problems. Someone call the wambulance.

/sarcasm Someone should ask how Australia struggles to manage winter in July. Oh wait, they don't.

Just use TAI where no fucking hacks are needed, and get rid of this retarded leap second, leap year, and DST.

Re:Nut in charge of the nut house.

[Anonymous Coward]

Long before we start having winter in July on the northern hemisphere we will start to have to shift store opening hours since 12:00 isn't noon anymore. Given that we want business hours to coincide with daylight this would be a much bigger problem long before we have snow in July. And who cares what season is in what month. That is totally irrelevant. There are places, like Aruba, where there are no discernable seasons. Do they only have June because of this?

TAI is good for scientific purposes, but leap days, leap seconds and timezones are good for human society, as biological creatures dependent on sunlight we should adjust our timekeeping for the light. DST on the other hand is pointless. The places that need it the most, close to the poles, are the places where the difference due to adjustment disappears quickest. In just a few weeks the adjustment for DST has gone away due to the rapidly increase/decrease in lenght in daylight.

Re:Nut in charge of the nut house.

[Anonymous Coward]

That's from the Hitchhiker's Guide to the Galaxy. Hand in your geek card.

Re:Nut in charge of the nut house.

[Anonymous Coward]

Timezones are a best practice solution to a difficult paradox.

1) Noon is when the sun it highest in the sky
2) If it is Noon here, it should be Noon nearby
3) If it is Noon here, it is Midnight on the other side of the world

Obviously, once that third item was discovered, we needed a solution. One that gave each longitude its own time zone to the minute would have been 'more correct', but much more confusing as then there would be 1440 timezones, which would be hard to keep track of now, much less over a century ago. So they broke the earth into 24 timezones that all had the same minutes, and only differed by hours. Naturally, the boundaries have evolved politically, but the concept itself is sound.

Re:Nut in charge of the nut house.

[RockDoctor]

No. Get rid of this silly expectation that there needs to be a whole number of $NATURALTIMEUNIIITOFCHOICE$ in a $OTHERNATURALTIMEUNIIITOFCHOICE$.

The universe has as much need to coordinate Earth's rotation with the flatulence pulses of the bombardier beetle, as it has to coordinate $ThisLunarSolarEclipse$ with $ThatEuropaIoMutualEclipse$. I.e. none at all.

This sort of adjustment is only an issue if you do it very rarely. If you deal with events more than a coupple of hours different from your local sun rise/set, on a regular basis, you don't find this a proble. You just put several clocks on your wall, with BIG SIGNs on th wall.

I'd like to keep the world in perfect sync

[Anonymous Coward]

Drink Coke! Or snort! Or shoot! JUST DO COKE!

Re:I'd like to keep the world in perfect sync

[Anonymous Coward]

Regular, Diet, with lime, or Zero?

receives 150,000 requests per second

[fustakrakich]

Not from me it doesn't. I only ask maybe once a month.

Re:receives 150,000 requests per second

[Anonymous Coward]

I would say more than that I think windows by default asks once a week and pretty much everyone has more than one device connected to the internet and im pretty sure everything updates time automatically

Re:receives 150,000 requests per second

[sexconker]

I'm guessing they meant NTP traffic is estimated to be 150,000 requests per second, globally.
All my machines sync to their domain controllers. The domain controllers sync to a local time server. The time server syncs to the big boy government time servers. They never see the flood of requests from my machines or the other machines at my location. They only see requests from our local time server.

Re:receives 150,000 requests per second

[fustakrakich]

I'm guessing I need to put in a laugh track. I usually turn off the automatic updates, including the time. *Paranoia strikes deep* You'd be amazed at how sloppy these crystals in our machines are at keeping time. 60 cycle hum is more accurate.

Re: receives 150,000 requests per second

[Anonymous Coward]

60Hz wall power is indeed accurate because power companies know it used as a time signal in some devices.

Re: receives 150,000 requests per second

[Anonymous Coward]

(Lameness hack) Are we there yet?
(Another hack) Are we there yet?
(Slashdot hack!) Are we there yet?
(Endless hacks) Are we there yet?
(Are we hacked?) Are we there yet?

Re: receives 150,000 requests per second

[threephaseboy]

It may not be that way forever.

Re:receives 150,000 requests per second

[Anonymous Coward]

lol, reloaded a netbook this weekend. System came up 2 DAYS off. Won't update FOR SECURITY reasons because the date is wrong. Odd excuse to say the least. Windows 7 yet used a discontinued windows time server :/

hehe, what a POS, took all day to reload itself from it's own HD.

Re:receives 150,000 requests per second

[LinuxIsGarbage]

Back in the Windows 9x days I remember adding a realmode program to autoexec that would compensate for natural drift in the clock. Sync the clock to atomic, sync it again in a week when it was way off, and then it would calculate the error and continuously apply it to the RTC. It worked surprisingly well.

To bad a similar algorithm is not still used.

Re:receives 150,000 requests per second

[Anonymous Coward]

That's essentially what NTP does. It runs in the background as a daemon and disciplines the local clock to keep it in sync with the upstream servers. It won't jump the time unless you tell it to, choosing instead to slow/speed the passage of time to stay in sync.

IIRC, the amount needed to discipline the local clock is stored in the drift file.

This all works very well as long as your clock crystal is mostly rational and doesn't jitter too much based on temperature variation.

Re: receives 150,000 requests per second

[inasity_rules]

I don't know about America, but over here I have seen the frequency vary from 49Hz to 52Hz as the grid gears up for the 6am winter load(everyone gets up and starts cooking/boiling a kettle etc). On average it is still probably accurate. I am fairly sure the US power companies do the same thing. It is difficult to control the frequency under varying load.

Re:receives 150,000 requests per second

[RockDoctor]

And that is the way it shoud be.

The only tinhg I'd consider adding would be a level-0-or-1 source, such as a GPS/ GLONASS time source (you can argue over whether that is level-zero, or level-one, validly), and some glue so that if your time system and the alternative system differ by more than $SENSITIVITY$, your sysadmins get an ... orange-not-red flag and are aware of the issue.

If you're doing very time sensitive work, that's a different issue. A large bucket of issues.

i'd like to keep the World in Sync

[turkeydance]

with my technology

Re:i'd like to keep the World in Sync

[suutar]

you'd like to buy the world a clock
and always wind the key?

Re:i'd like to keep the World in Sync

[Anonymous Coward]

oh entertain me then, what technology?
I'm in the mood for a knock knock joke from a ft etr

Illegal tech headline

[Anonymous Coward]

Tweeeeet!!! 5 minute penalty for using the correct "whose"! Next time, use "who's" so you fit it with all the other geeks who are unable to understand the apostrophe!

Re:Illegal tech headline

[Anonymous Coward]

apostrophe!

That's an exclamation mark!

bzzzzt

[epine]

TFA:

the newest of which is so accurate, it gains or loses only a second every 300 million years

First of all, that's aspirational (or was) in most of the other articles I found.

Contra TFA: NIST Launches NIST-F2

Primary standards such as NIST-F1 and NIST-F2 are operated for periods of a few weeks several times each year to calibrate NIST timescales, collections of stable commercial clocks such as hydrogen masers used to keep time ... Technically, both F1 and F2 are frequency standards, meaning they are used to measure the size of the SI second and calibrate the "ticks" of other clocks.

Unfortunately, even contra TFA is weak geek tea:

Both NIST-F1 and NIST-F2 measure the frequency of a particular transition in the cesium atom—which is 9,192,631,770 vibrations per second, and is used to define the second, the international (SI) unit of time.

I guess there's a reason why people with tiny UIDs memorize pi to a silly number of places: it helps you not leave off the other five or six significant digits in the rare case where it actually matters. The real frequency standard is only, like, approximately a million times better than that long-assed, dock-tailed string of digits visually implies.

Truly inconceivable—almost—and yet barely able to time slice the total perspective vortex.

Finally, some obligatory geek porn: Atomic fountain

Re:bzzzzt

[KGIII]

Pfft... Real geeks know (and understand!) the Bailey, Borwein, and Plouffe Formula and a dozen ways to implement it in C.

I'd like to have you come on time

[swschrad]

and work a whole damn day
if you don't get your butt in gear
you won't get no more pay!

Time is a social construct

[PopeRatzo]

I no longer believe in time. I think it's pretty much junk science, and the daylight savings time thing is just an Illuminati plot to keep us subservient to the elite.

You all can do what you want, and spring forward or what not if you need to bend your will to The Man, but I ain't changed my clocks since 2007 and haven't noticed one thing. In fact, I couldn't change them since I threw out my wristwatch, Easy Rider-style, in 2006. Right now, if I look down at the time display on my screen, it's flashing 00:00:00, just like my DVD player and microwave.

Re:Time is a social construct

[Anonymous Coward]

I no longer believe you take yourself seriously or ever form coherent sentences at all, instead preferring to go through life just rambling whatever incoherent jumble of words produces itself from the mass of diseased tissue you call a brain.

Re:Time is a social construct

[KGIII]

Well, when you're old like us, you just say whatever you damned well feel like saying and damn the consequences or opinions.

Me? I think most people's feet are ugly and there's not a damned thing they can do about it.

Re:Time is a social construct

[neminem]

You forgot to mention how we were all educated stupid.

Re:Time is a social construct

[JonnyCalcutta]

That's not true. I used to have some great shoes that made my feet look great. Of course that was back in the day when they really knew how to make good shoes. Nowadays even Doc Martins have gone downhill and pretty much all shoes are glued rather than stitched.

Its the same with hats. One size fits all? Bollocks more like.

Re:Time is a social construct

[PopeRatzo]

I no longer believe you take yourself seriously or ever form coherent sentences at all, instead preferring to go through life just rambling whatever incoherent jumble of words produces itself from the mass of diseased tissue you call a brain.

Honey, is that you?

Re:Time is a social construct

[LinuxIsGarbage]

I no longer believe you take yourself seriously or ever form coherent sentences at all, instead preferring to go through life just rambling whatever incoherent jumble of words produces itself from the mass of diseased tissue you call a brain.

I initially read this as "deceased". It had the same effect.

Re:Time is a social construct

[Anonymous Coward]

If there is no time, than what does that mean for timecube?
https://en.wikipedia.org/wiki/Time_Cube

Re:Time is a social construct

[SuiteSisterMary]

Time is an illusion. Lunchtime doubly so.

nist?

[Frederic54]

I am using time.nrc.ca as my reference (I don't think it is a stratum 1 however)

Re:nist?

[Anonymous Coward]

stratum 2.

Road Trip...

[pr0fessor]

"What time is it?" 6 Billions times a day...

Sounds like a long road trip with my kids... Are we there yet, How much farther, When will we be there, What time is it

Trading Systems?

[Midnight Thunder]

I thought trading system typically relied on GPS based NTP servers in their own network?

Oh and if you want to make your one: http://www.satsignal.eu/ntp/Ra... . While probably not as accurate as a commercial version, it is a tad slight cheaper.

Re:Trading Systems?

[Anonymous Coward]

You'd still need a reference time keeper to ensure there's no drift in your (or even their) systems. Everyone synchronises with the official timekeeper.

Note: If there was drift in every other system in the world except yours then that will have the inverse effect on you. In fact the earth's slow degradation as a time keeper is why we have leap seconds.

Does anybody really know what time it is?

[93 Escort Wagon]

Does anybody really care?

Re:Does anybody really know what time it is?

[93 Escort Wagon]

Wow, somebody with mod points really isn't a fan of Chicago!

dst

[Anonymous Coward]

my pc's clock is off by an hour.. can you fix that please? and while you're at it, can you also fix the phone, dvr (and associated network schedules), and car, too?

Horrible mostly wrong article title

[Anonymous Coward]

Judah Levine, the gentleman mentioned in the article, built interfaces to existing atomic clocks that allowed other clocks to synchronize with them, which is a worthy achievement.

But today, the vast majority of synchronized clocks are being kept synced by NTP across the Internet, not by radio signals. And although Levine also implemented NTP interfaces at NIST, he didn't invent NTP nor was he responsible for its dominance of Internet timekeeping.

The man who invented NTP and originally wrote the implementation was David L. Mills of the University of Delaware.

Mills is also the man who created the Fuzzballs and EGP, making global-scale internetworking possible.

Re:Horrible mostly wrong article title

[Ungrounded Lightning]

The man who invented NTP and originally wrote the implementation was David L. Mills of the University of Delaware.

Mills is also the man who created the Fuzzballs and EGP, making global-scale internetworking possible.

I knew Dr. Dave when he was still at the University of Michigan, doing the Data Concentrator and the Language Lab's automation, and I was in high school and hanging around the campus.

Great guy.

Re:Horrible mostly wrong article title

[Standfast]

Thank you. I deeply lament David Mills's absence from the original article. He should at least have been mentioned, as he deserves far more credit for innovation in distributing time than does Judah Levine, while still intending no disrespect for Dr. Levine.

Teach don't preach

[Anonymous Coward]

There's a lot of false assumptions being made in this thread. Humans introduced this craziness of leap seconds in an effort to more accurately understand time. We made a big mistake last time we tried to recalibrate which no has us doing this leap second dance. This video clearly explains the Leap Second: https://www.youtube.com/watch?v=RuPQsqZaq8A

Like "man" from Cheech and Chong

[merlock]

I'm not into time...