What causes the unpredictability in this? I would have guessed we have earth's rotation and orbit down to many decimals. Does geological activity, weather, or something else cause rotation speed differences that we just can't predict?
Since I was checking the Wikipedia article anyway (for when the last leap second was inserted), it also has an answer for this:
"Because the Earth's rotational speed varies in response to climatic and geological events, UTC leap seconds are irregularly spaced and not precisely predictable."
Yes, all of those and more. Our measurement precision is much better than the year-to-year first and second derivatives of day length. https://datacenter.iers.org/singlePlot.php?plotname=Bulletin... has the most relevant plot to this; the vertical jumps reflect leap seconds. (IERS has other plots for other dimensions of rotation, but I like this one.)
Seems like the seasonal change in June-October increased
My best guess would be it's somehow related to water distribution? More water going into the atmosphere? Glaciers growing (unlikely)? Did multiple huge water reservoirs go into service and get filled up over the summer months?
In short, yes, the weather, geology, and signicantly, human movement of water via aquifer draining and dam building, as well as glaicial and ice melts, all contribute to unpredictable changes in the earths rotational period, as well as the axis of rotation. The models for this are IIRC trigonometric polynomials of fairly low order, so even if we could model the unpredictability perfectly, truncation error would limit our ability to distribute the model at super high accuracy. The existing models are built in to, eg, satellites, so you can't just make them arbitrarily complex.
Fun fact: leap seconds will stop being a thing soonish. I think they phase out in 2035, with a delay because Russia needed time to update glonass satellites.
(Note: on mobile, this is from memory, details need checking ;))
A frightening fact, the 2011 magnitude 9.0 Tohoku Earthquake shifted the position of the Earth's figure axis about 17 centimeters, making days about 1.8 microseconds shorter.
Everybody agreed that "Leap seconds" are a sufficiently bad idea that they should be replaced by 2035. Nobody has agreed how to fix it, and "Just turn them off" isn't technically legal. However, "What if there were Leap hours instead?" is technically legal and of course those hours would happen in the very distant future (likely after our civilisation is gone) so it's functionally identical to "Just turn them off" but without legal problems.
Now, I'm English, and England loves this sort of hack. You may have heard that controversial UK politician Nigel Farage "resigned" as a Westminster MP recently and that's not technically true because you can't resign, historically people hated that job and so you can't resign and we never changed that, but what you can do, and everybody does, is get assigned an "Office of profit" in which legally the King is paying you, an MP can't work for the King so you can't be an MP any more. The "Offices of profit" in question aren't real jobs† and don't pay real money, like this "Leap Hour" they'd be a legal fiction. So everybody says you "resigned" but in fact you legally can't do that...
† I mean, historically they were real jobs that made sense which is why the King paid somebody to do them, but England is very, very old so they haven't made sense for centuries and serve only as a legal fiction today.
There's a long tradition in the UK of having electoral candidates who don't expect to win but run because it's free publicity in a high profile race. "Count Binface" is a comedian who dresses up as a space alien whose outfit resembles well, having a Bin for a face. The serious political parties told Nigel to fuck off, if he wants to step down and then immediately contest the same seat they wouldn't run against him in this farce, but Binface isn't a serious politician so he is running in that by-election.
Nigel wanted to be able to do this whole thing about how the establishment is rotten and he (Wealthy public schoolboy who keeps lying to people and doesn't bother going to Parliament even though he was elected to do so) is a true man of the people and can put things right. It got him this far in life. But with the other candidate on your ballot being a space alien it's obvious which of these options is really "the establishment" and it's not the guy whose policies include "Building at least one house†" and who says he comes from a different planet...
† British political parties often insist they will build lots of housing because that's popular with voters. But, in practice they don't tend to really deliver because the various groups lobby not to actually build. So "at least one house" is a joke about this phenomenon, while conveniently also being technically possible, Binface could just build a house, that's a thing you can do.
I think it's more than publicity. Anyone can stand as a candidate, and anyone can vote for them. Money and connections and establishment and everything else don't matter, all candidates are equal on that stage. It's both weird and to be admired.
Nigel Farage has decided to counter a scandal by throwing himself upon his constituents for judgement, the obviously establishment parties have backed off to allow Binface to run against him in a ~1v1, and you think Binface is more anti establishment than Farage?
This seems like an interesting solution, even if it's absurdist at first thought. What if we just shift the steel bar in Greenwich 20 metres east or west instead of adding a leap second?
Then everything would theoretically be correct. The logical next thing to do would be to move all the time zones as well. But time zones already don't coincide with the lines of longitude in practice; they tend to follow country or internal boundaries somewhat close to the lines of longitude (but sometimes multiple hours away!). After a few thousand leap seconds, maybe one or two countries would feel it was helpful to readjust a time zone boundary to better align with solar time, but in practice this would never be the overriding reason for that decision.
You say people's GPS systems would all suddenly be wrong because they depend on locations in latitude and longitude? I don't think this is a problem either: in practice longitude and latitude are given not relative to the steel bar in Greenwich, but to per-continent geodetic datum points. This already prevents continental drift from affecting your coordinates, though a big earthquake can still mess things up.
On the subject of amusing British political legislation, should he defeat Nigel Farage in the resulting by-election Count Binface will not be able to wear his costume in Parliament; not only is business attire required in the House of Commons, it's specifically forbidden to wear a suit of armour there due to a law from the 14th century.
For those unaware, the major parties have declined to participate in the by-election triggered by Farage's resignation seeing the whole thing as a farce. As a result Farage will likely face only Count Binface, a space warrior from Sigma Six. He'd get my vote purely on the basis that he's promised to bring back Ceefax, and build at least one affordable house.
Quite a few MPs in Westminster already don't take their physical seats in Parliament (and never vote or address the House) because the conditions attached to doing so aren't compatible with their principles. Maybe Count Binface will be the next.
More specifically, that refers to the Northern Irish MPs from the Sinn Féin party who do not recognise the UK Crown as a lawful authority in NI, and hence, refuse to take an oath of allegiance to it. (They used to not recognise the Republic of Ireland as well, until the 1980s I think.)
It's understood by constituents that a vote for a Sinn Féin representative is a protest vote that results in specifically nobody going to Westminster to represent you. I cannot imagine that any significant number of people vote for them and are then astonished when this has the effect everybody else expects.
On the other hand, Binface has not, as I understand it, ever said he would not serve if elected. He's made it clear that he's not from Clacton (or Makerfield) -- because he's a space alien -- but I believe he said if he won he would move there so that's fair enough if the constituents want him. They previously elected Nigel, and he's rarely in either parliament or Clacton so Binface can't be worse than that.
Basically we guessed wrong. We thought knowing "Solar time" would be more useful than in it, and we thought these "Leap seconds" would be less trouble than they are.
It's like you buy a cat to help with your rodent problem, figuring the cat will eat mice and isn't much trouble to look after, but after purchasing a cat you find that your problem was actually rats, your cat is terrified of these large dangerous creatures and sometimes gets bitten by them necessitating expensive vet bills and now you need to pay a lot of attention to the poor animal and also now need to buy cat food.
Heh, I like the analogy but my question was really why it was considered such a hassle.
I mean we deal with daylight saving time all the time and I know it's not the same because the leap second affects UTC, not just local time zone, it's just that you are either dealing with monotonically increasing time like epoch, or you are dealing with "human" time and I found no distinction in the latter.
Is it "just" that leap seconds or delay seconds caused problems in epoch to utc conversion? Note the just in quotes, but did I just answer my own question? :)
The co-ordinated universal time, UTC exists by international agreement. In the 1960s lots of countries signed a treaty so that's the "authority" AIUI.
The treaty says everybody agrees that this new standard will try to track "solar time" which felt intuitively reasonable. They want something equivalent to the old GMT which was really based on solar time, except more modern. At first the idea was, well, we just work out how fast this damp rock spins more precisely and we can use that to ensure everything works forever.
More precise measurements of the damp rock showed that, annoyingly, Mother Nature did not provide the spinning rock as a precise clock, it spins slower and faster according to a huge number of variables and so the best we can do is measure the spinning against an actual clock. So, "Leap seconds" were born to meet that legal requirement to have UTC match the solar time.
The "leap hour" would likewise fulfil this requirement, just in a deliberately useless way because we actually do not care about precisely tracking solar time. If we did, almost every human in the world would be perpetually annoyed because of course our present system of "time zones" means on average we're at least 30 minutes wrong!
Everybody agreed that "Leap seconds" are a sufficiently bad idea
No. Not everybody. I prefer accurate time, and all the complaints I've heard hold little water.
My servers need to timesync forwards and back all the time, eg timedrift. They need to jump to new times, or slowly drift, depending.
VMs can be hypervisor starved, or need to move to a new host.
Servers also need to handle missing time. Any daemon or program which cannot handle this is buggy, broken, and needs to deal.
Leap seconds are just part of all of this, and present no new issues compared to normal time change. I question the capabilities of any engineer who singles out time second as difficult to deal with, time is constantly changing on servers. Constantly.
So back to the start, no... everybody doesn't agree. Google isn't "everybody".
Accurate to what though, and for what? We decide what the standard is, and it seems like it would be a lot easier to have accurate time if we aren’t adding or subtracting seconds here or there. Does it really matter if the sun crests the horizon a second earlier than it did ten years ago? If it does, isn’t it much easier to just adjust your sun-cresting time?
> because Russia needed time to update glonass satellites.
Why is this? As leap seconds don’t occur on a regular frequency, I assume they are not hardcoded on the software or hardware on board, but the control centre uploads them on the satellites enough in advance once they have been scheduled. So why can’t the control centre just stop sending those updates?
My understanding the problem is that GLONASS is aware of leap seconds at all. It sends messages in UTC, which has this leap second funny business. GPS uses a special "GPS time" (sometimes abbreviated UT) that doesn't have a leap second. For further confusion, the leap second ensures that UTC is never more than 0.9 seconds off of mean solar time, aka UT1.
This type of assumption that was made early in a massive software and hardware project that's now been ossified for ~50 years is going to be hard to change.
Among other things, turbulent currents of liquid iron in the Earth's core can make the core drift eastward or westward, which causes the crust and mantle to turn slower or faster. Same thing with the strength of the jet stream.
UNIX timestamps are fully ignorant of leap seconds, i.e. pretends they don't exist. That means there can be physical seconds of time that cannot be referenced with a UNIX timestamp (when a leap second is inserted) as well as UNIX timestamps for seconds that don't exist (when a leap second is deleted).
It also means that if you subtract two timestamps, you might not get the actual time between them. Though this is also true of most ways of representing time (TAI being a notable exception).
Whenever leap seconds were added, Google was running the clocks on their servers slower/faster over a longer period of time (hours) so they would slowly drift back in sync with the solid platinum, perfectly spherical grandfather's clock sitting in NIST or whatever: https://developers.google.com/time/smear
For those who need more context of who the Time Lords are
The Time Lords are a fictional ancient race of extraterrestrial people in the British science fiction television series Doctor Who. In-universe, they hail from the planet Gallifrey and are stated to have invented time travel technology.
I think if we're being pedantic, the character's name is "The Doctor". The TV show is named "Doctor Who" but the character doesn't call themself that and a name is what something is called.
[Edited to avoid assigning a gender to a character who has had different genders]
> This means the atomic clock is behind the solar clock by 37 seconds?
If anything, it's the other way around.
A UTC day is defined as exactly 86400 SI seconds. But an actual mean solar day is a few milliseconds longer (although the difference is not constant due to irregularities in the Earth's rotation--but the average difference is expected to slowly increase over time). SI seconds are counted by atomic clocks, so UTC advances its day by one every 86400 atomic clock seconds.
But a solar clock that advances its day by one every time the mean sun reaches noon (it has to be the mean sun because the rate at which the actual sun moves across the sky varies over the course of a year, we need to look at the average) will advance its day a few milliseconds later than UTC does. Or, to put it another way, each time period that the solar clock says is exactly 86400 seconds, is a few milliseconds longer according to the atomic clock.
As this happens day after day, the difference accumulates, and when it gets close to being a full second, a leap second gets inserted into UTC, so that one of its days is 86401 seconds long instead of 86400. The reason for this is that UTC is not just counting atomic clock time; it also has to stay in sync with where the sun is in the sky since so many human activities are tied to that. And we humans have defined "in sync with the sun" to be "within a second of the average sun". In other words, we want UTC noon to be within a second of mean solar noon on the prime meridian.
So the 37 seconds is how far mean solar noon would be behind UTC noon, if we didn't use leap seconds--at UTC noon, the mean sun would be 37 seconds short of actually crossing the prime meridian in the sky.
"In other words, we want UTC noon to be within a second of mean solar noon on the prime meridian."
Why?
If I travel 1 mile east or west of the prime meridian, my solar noon now comes 2-3 seconds earlier/later. It's nearly impossible to have your local time match your local solar noon. For most of the population, solar noon is, on average, 30 minutes off of 12:00 noon.
For things that need much more precusion than my lunch, ±1 second probably still isn't good enough, so they need another layer of correction anyway. Given that exists, might as well push leap seconds into that layer too.
Um, because it's the prime meridian and that's how UTC is defined?
> It's nearly impossible to have your local time match your local solar noon.
Which is why I specified on the prime meridian, which is the particular local meridian that UTC is defined as corresponding to.
> solar noon varies from day to day by 10-20 seconds.
Which is why I was careful to specify mean solar noon.
I'm not quite sure what your issue is. Yes, we have time zones tied to specific meridians, and the actual sun's speed in the sky varies (which I mentioned in my post, so I'm not sure why you seem to think I'm unaware of it) so in most places local time by the clock doesn't match local time by the sun. Yes, a leap second adjustment to UTC is quite a bit smaller, taken in isolation, than the annual variation in actual solar time vs. mean solar time.
But over time, if we didn't have leap seconds, the difference would accumulate. The accumulated difference now between UTC and TAI is 37 seconds--which is almost twice the maximum variation in actual solar noon from mean solar noon that you refer to. We humans have collectively decided that we don't want that, and that it's better to do the adjustments a little at a time rather than in bigger lumps.
"But over time, if we didn't have leap seconds, the difference would accumulate. The accumulated difference now between UTC and TAI is 37 seconds--which is almost twice the maximum variation in actual solar noon from mean solar noon that you refer to."
No, the 10-15 seconds I mentioned is the daily variation in solar noon.
From the link I posted, in NYC, solar noon on 2026-01-01 is at 11:59am. On 2026-01-31, solar noon is at 12:09pm. In one month, it has drifted 10 minutes. That's much greater than the 37 leap seconds we have added in 60 years.
"We humans have collectively decided that we don't want that, and that it's better to do the adjustments a little at a time rather than in bigger lumps."
Yet we just reversed that decision. No more leap seconds after 2035. After trying it, we decided it was terrible.
> the 10-15 seconds I mentioned is the daily variation in solar noon.
Yes, but averaged over an entire year, it still comes out to zero. The difference between mean solar and atomic time does not. It accumulates over the years.
> we just reversed that decision
We paused it for 100 years after 2035. That doesn't change the physical fact that the Earth's rotation will continue to slow over the long term. We might eventually decide to just not care about that when it comes to civil timekeeping, but that's not what the decision you're referring to did. It just said we can afford to let the difference between UTC and TAI accumulate from 2035 to 2135 (by which time it is predicted to be about a minute) while we figure out what we want to do over the longer term.
There's a graphic novel by Cixin Liu "The Wandering Earth" where they not only stop Earth's rotation with this method, but also propel Earth out of the solar system (for what appear to be good reasons, I might add). Can't quite remember what fuel they used for the engines.
They are good reasons. Conspiracy theorists are able to persuade almost everybody that the reasons were bullshit, an excuse to seize power or something, and so the few who still insist this was necessary and mustn't stop are executed. Almost immediately after those executions, Mother Nature proves them right. So that leaves everybody: Guilty of having murdered their saviours and with no choice but to carry on with the very plan they had insisted was bogus...
There is a Chinese movie but I'm kinda surprised no Hollywood studio got themselves a rights deal and made a US-friendly movie where the Sun conveniently blows up slightly earlier and our heroes are vindicated and everybody agrees they were right all along.
IIRC they accelerated rock as the reaction mass. Gigatons of rock accelerated to well above escape velocity and launched from the ground.
In the real world their scheme is doomed as it would strip the atmosphere off of the Earth, but since they were planning to leave the solar system the atmosphere was going to freeze to a solid anyway so maybe it didn't really matter. To be honest I thought the entire scheme was an extremely elaborate cover for the fact the lead ship was the actual ark and everyone else was just plain doomed. This would have mirrored one of the themes in the 3 Body Problem where interstellar space travel is strictly forbidden until everybody can participate at once. The "launch the Earth as a spaceship" concept was so poorly thought out I thought it had to be a fraud in the story, and our somewhat dense protagonists just didn't catch on.
Wouldn't it just be easier to have Superman fly around the planet a bunch of times really fast to do the same thing? Then you wouldn't have to worry about having to deal with all of that engine maintenance.
You could actually move very large quantities of water around and probably have a measurable impact. Like draining the California central valley aquifer.
I've often dreamed of and revisited this idea. I first started thinking of it seriously when I realized I was paying the same rent in February as in January despite a significantly shorter-than-mean (30.4375) month...!
My ideal year is 12 months, each 5 weeks long, each week 6 days long. At the summer solstice, 3 intercalary days (bank holidays), at the winter solstice, 2 or 3 intercalary days depending on leap year.
Leap seconds are not added on a regular schedule like leap days, they depend on physical measurements of Earth. So high reliability systems with comprehensive timekeeping would not be perturbed by these choices, I would think.
It’s a huge problem. The most common approach to address it is called smearing; the duration of each second for a 24 hour period ahead of the “leap” is adjusted. For strict ordering systems this works as each device maintains time sync with the global clock, the duration of a clock cycle is just slightly different. I think this was in the original Spanner paper, actually.
Some rare systems use monotonic oscillator seconds and ignore the earth rotation second, but if you ever have to translate those to real time, you get an accumulating disaster over time and it’s generally regarded as not a good idea.
Clocks used to be able to use the 60Hz cycle to track time, and grid providers would run slightly slow or fast ("time error correction") to get back into sync. A leap second would just be part of this.
I believe in the US this error correction has been discontinued in the East and in Texas, but is still done in the West for some kind of non-clock "inadvertent interchange" reasons I don't understand.
A few years ago, a dispute between Kosovo and Serbia caused the entire European grid to drift away from 50.000Hz down to 49.996Hz. Millions of microwave clocks across the continent ended up 6 minutes late: https://hackaday.com/2018/03/09/europe-loses-six-minutes-due....
According to Wikipedia [0] the headquarters of IERS (International Earth Rotation and Reference Systems Service) is in Frankfurt, Germany (contact information on their website [1] has an address in Frankfurt too). The web server hosting the linked file also contains German text in its error page:
> Dieser URL wird nicht beantwortet. Bitte wenden Sie sich mit Ihrer Anfrage an das Bundesamt fuer Kartographie und Geodaesie.
Leap days, February 29th, are not at the level of time zones. Different time zones do not disagree as to when March 1st will occurs immediately after February 28th.
god that would be awful. Can you imagine time zones being one second off from each other. Or two or three? ah yes, india is GMT+4:30:03, where europe is GMT+0:59:58
I had not seen that. In the nineties I worked on an alerts system where you could sign up for like some sport or weather data at a certain time of day. We stored the alert times as minutes before midnight and then ran the time to trigger calculations often enough that unless you were some freak that wants weather alerts at 2 am it basically worked to send one alert each day at the appropriate time; we had a special non-OS copy of the tzdb as the users were global. One quarter I forgot to update it and everyone in Mexico City got their alerts one hour off till someone complained and I updated it. We also had data feed alerts, like score changed or stock hit x% over previous high, where the problem is some data is manually entered and can be off by a factor or two of ten from time to time. Had to be filtered. I had a lot of fun.
Right, and orders of magnitude more people have to deal with UTC and timezones compared to TAI and the offset. So it's good to have it in the layer that it's in
The changes in Earth's rotational speed that leap seconds help account for affect the whole globe. Why shouldn't the effects be noted in the global time standard?
Don't we handle them mostly the same? In a leap year, the month of February gets a 29th day, labeled 29. On a leap second, one of the minutes gets a 61st second, labeled 60. Or we drop the 60th second, and second 58 is followed by second 00 of the next minute.
The notable differences are that
1) the leap second happens at the same time globally (23:59:60 UTC), while leap days start at 00:00 local time
2) leap seconds happen at irregular intervals
3) leap seconds are nearly universally implemented wrong, because the ability to show :60 on a second display for for one second at most twice per year is just not worth the implementation complexity
You could argue about 1, but the alternative would lead to much more complicated timezone math (time zones can be an additional one second apart from each other depending on whether the leap second is already applied) for very limited benefit. Number 2 seems unavoidable, and 3 is entirely unintended, just the way things have worked out in real life
The leap day system handles the mean, the leap seconds handle the variance around the mean. The need for leap seconds is not predictable—they zero out accumulated error.
That would create much more chaos, because every region autonomously decides on its timezone(s). You'd have different countries and/or timezones using different leap second counts.
Yes! I yearn for the day when central daylight savings time is 1:00:00:36 behind eastern time, but standard central time remains offset by 1 hour exactly (except for leap years, which are obviously 1:00:00:36 offset all year round).
Not anymore forever. We’re just not adding one for this year. We might need one next year, we might not. It all depends on the Earth’s rotation and orbit
I don't think it's cowardice, is it? The graph at https://en.wikipedia.org/wiki/Leap_second seems to indicate that adding a negative leap second at this point in time would be improper. (We're ~+0.1s off, and a negative leap second would occur if the line was approaching +0.6s. I'd like one too just for the curiosity of the thing, but … the Earth isn't having it.)
There's an opportunity to insert or remove a leap second twice a year. They only decide about 6 months in advance of each opportunity what to do (leap second, skipped second, or do nothing).
This announcement is very much a nothing burger; it’s already been more or less decided that adding leap seconds just isn’t going to be a thing anymore (in our lifetime). Here’s on article from 2022: https://www.timeanddate.com/news/astronomy/end-of-leap-secon...
In practice it will never affect anyone because it's a legal fiction, but even if you pretend to believe we would actually introduce this "leap hour" it would be in the distant future long after we're all dead and if there are still humans who have any idea the year 2026 happened they're not sure which of Donald Trump, Taylor Swift, Tony Stark and John McClane were real people.
Edited to add:
This is such a ridiculously long time frame that they might not be sure whether we were worried about climate change, for them that's either a disaster they survived (and maybe most didn't) or it's a weird blip in their historical charts which they struggle to explain. Did our civilisation do something very, very stupid? There is a flammable gas deep underground, did we set fire to it because we were crazy? Why the hell would we have done that? There are signs we deliberately set fire to the coal which is a toxic rock also found underground? That would explain the global climate going nuts. Maybe it was a ritual or something. Ancient people are mad.
Up until now we have added 1 leap second every 2 year (27 leap seconds since 1972). So if it continues like this, in 7200 years it would be 1 whole hour, and in "only" 3602 years it will be closer to the next hour than the previous (so a natural time to add the leap hour).
What causes the unpredictability in this? I would have guessed we have earth's rotation and orbit down to many decimals. Does geological activity, weather, or something else cause rotation speed differences that we just can't predict?
Since I was checking the Wikipedia article anyway (for when the last leap second was inserted), it also has an answer for this:
"Because the Earth's rotational speed varies in response to climatic and geological events, UTC leap seconds are irregularly spaced and not precisely predictable."
https://en.wikipedia.org/wiki/Leap_second
Yes. Geological activity, movement in the outer core, atmosphere, oceanic currents, melting ice, earthquakes, to name a few.
Earths rotation has been unusually fast lately. So there is not enough drift to warrant a leap second.
Yes, all of those and more. Our measurement precision is much better than the year-to-year first and second derivatives of day length. https://datacenter.iers.org/singlePlot.php?plotname=Bulletin... has the most relevant plot to this; the vertical jumps reflect leap seconds. (IERS has other plots for other dimensions of rotation, but I like this one.)
Very interesting, I wonder what happened in 2020 that causes the rotational speed to start drifting the other way?
Pandemic -> more people working from home -> less people in tall office buildings -> faster rotation (like a skater pulling in their arms).
Probably not remotely true but it would be funny.
Seems like the seasonal change in June-October increased
My best guess would be it's somehow related to water distribution? More water going into the atmosphere? Glaciers growing (unlikely)? Did multiple huge water reservoirs go into service and get filled up over the summer months?
I know the Three Gorges Dam added ~0.06 microseconds on its own, so the effect of reservoirs definitely is noticeable. https://www.jpl.nasa.gov/news/nasa-details-earthquake-effect...
In short, yes, the weather, geology, and signicantly, human movement of water via aquifer draining and dam building, as well as glaicial and ice melts, all contribute to unpredictable changes in the earths rotational period, as well as the axis of rotation. The models for this are IIRC trigonometric polynomials of fairly low order, so even if we could model the unpredictability perfectly, truncation error would limit our ability to distribute the model at super high accuracy. The existing models are built in to, eg, satellites, so you can't just make them arbitrarily complex.
Fun fact: leap seconds will stop being a thing soonish. I think they phase out in 2035, with a delay because Russia needed time to update glonass satellites.
(Note: on mobile, this is from memory, details need checking ;))
> as well as the axis of rotation
A frightening fact, the 2011 magnitude 9.0 Tohoku Earthquake shifted the position of the Earth's figure axis about 17 centimeters, making days about 1.8 microseconds shorter.
2035 is the agreed drop dead date.
Everybody agreed that "Leap seconds" are a sufficiently bad idea that they should be replaced by 2035. Nobody has agreed how to fix it, and "Just turn them off" isn't technically legal. However, "What if there were Leap hours instead?" is technically legal and of course those hours would happen in the very distant future (likely after our civilisation is gone) so it's functionally identical to "Just turn them off" but without legal problems.
Now, I'm English, and England loves this sort of hack. You may have heard that controversial UK politician Nigel Farage "resigned" as a Westminster MP recently and that's not technically true because you can't resign, historically people hated that job and so you can't resign and we never changed that, but what you can do, and everybody does, is get assigned an "Office of profit" in which legally the King is paying you, an MP can't work for the King so you can't be an MP any more. The "Offices of profit" in question aren't real jobs† and don't pay real money, like this "Leap Hour" they'd be a legal fiction. So everybody says you "resigned" but in fact you legally can't do that...
† I mean, historically they were real jobs that made sense which is why the King paid somebody to do them, but England is very, very old so they haven't made sense for centuries and serve only as a legal fiction today.
Farage is such an ass, the King should make him feed donkeys or something.
"Vote Count Binface and Bin the Cunt" :D
There's a long tradition in the UK of having electoral candidates who don't expect to win but run because it's free publicity in a high profile race. "Count Binface" is a comedian who dresses up as a space alien whose outfit resembles well, having a Bin for a face. The serious political parties told Nigel to fuck off, if he wants to step down and then immediately contest the same seat they wouldn't run against him in this farce, but Binface isn't a serious politician so he is running in that by-election.
Nigel wanted to be able to do this whole thing about how the establishment is rotten and he (Wealthy public schoolboy who keeps lying to people and doesn't bother going to Parliament even though he was elected to do so) is a true man of the people and can put things right. It got him this far in life. But with the other candidate on your ballot being a space alien it's obvious which of these options is really "the establishment" and it's not the guy whose policies include "Building at least one house†" and who says he comes from a different planet...
† British political parties often insist they will build lots of housing because that's popular with voters. But, in practice they don't tend to really deliver because the various groups lobby not to actually build. So "at least one house" is a joke about this phenomenon, while conveniently also being technically possible, Binface could just build a house, that's a thing you can do.
I think it's more than publicity. Anyone can stand as a candidate, and anyone can vote for them. Money and connections and establishment and everything else don't matter, all candidates are equal on that stage. It's both weird and to be admired.
And a bit of "if Farage really wants the seat, he can fight for it". There's something unsporting about letting him win unopposed.
Nigel Farage has decided to counter a scandal by throwing himself upon his constituents for judgement, the obviously establishment parties have backed off to allow Binface to run against him in a ~1v1, and you think Binface is more anti establishment than Farage?
Next we need someone running on a platform promising "Truth, Justice, Freedom, Reasonably Priced Love, and a Hard-Boiled Egg"
just move the prime meridian. the one we use for timekeeping doesn't have to aligh with longitude forever.
This seems like an interesting solution, even if it's absurdist at first thought. What if we just shift the steel bar in Greenwich 20 metres east or west instead of adding a leap second?
Then everything would theoretically be correct. The logical next thing to do would be to move all the time zones as well. But time zones already don't coincide with the lines of longitude in practice; they tend to follow country or internal boundaries somewhat close to the lines of longitude (but sometimes multiple hours away!). After a few thousand leap seconds, maybe one or two countries would feel it was helpful to readjust a time zone boundary to better align with solar time, but in practice this would never be the overriding reason for that decision.
You say people's GPS systems would all suddenly be wrong because they depend on locations in latitude and longitude? I don't think this is a problem either: in practice longitude and latitude are given not relative to the steel bar in Greenwich, but to per-continent geodetic datum points. This already prevents continental drift from affecting your coordinates, though a big earthquake can still mess things up.
The GPS meridian doesn't align with the steel(?) bar anyway. There's a Tom Scott video about it.
On the subject of amusing British political legislation, should he defeat Nigel Farage in the resulting by-election Count Binface will not be able to wear his costume in Parliament; not only is business attire required in the House of Commons, it's specifically forbidden to wear a suit of armour there due to a law from the 14th century.
For those unaware, the major parties have declined to participate in the by-election triggered by Farage's resignation seeing the whole thing as a farce. As a result Farage will likely face only Count Binface, a space warrior from Sigma Six. He'd get my vote purely on the basis that he's promised to bring back Ceefax, and build at least one affordable house.
Quite a few MPs in Westminster already don't take their physical seats in Parliament (and never vote or address the House) because the conditions attached to doing so aren't compatible with their principles. Maybe Count Binface will be the next.
More specifically, that refers to the Northern Irish MPs from the Sinn Féin party who do not recognise the UK Crown as a lawful authority in NI, and hence, refuse to take an oath of allegiance to it. (They used to not recognise the Republic of Ireland as well, until the 1980s I think.)
It's understood by constituents that a vote for a Sinn Féin representative is a protest vote that results in specifically nobody going to Westminster to represent you. I cannot imagine that any significant number of people vote for them and are then astonished when this has the effect everybody else expects.
On the other hand, Binface has not, as I understand it, ever said he would not serve if elected. He's made it clear that he's not from Clacton (or Makerfield) -- because he's a space alien -- but I believe he said if he won he would move there so that's fair enough if the constituents want him. They previously elected Nigel, and he's rarely in either parliament or Clacton so Binface can't be worse than that.
> Count Binface
I did not expect this to be a real person. Is he with the Standing At The Back Dressed Stupidly And Looking Stupid party?
Hilariously, no.
That would be the Monster Raving Loony party who will apparently also be standing in this by-election. Count Binface has ruled out a pact with them.
I was very disappointed to hear that the Monster Raving Loony party is deciding to stand and split the vote.
I thought this was an opportunity for them to be tactical, but no.
(this is a joke)
So, it's solving a real problem, why are we dropping it? I mean, why does everybody agree it's a bad solution?
Basically we guessed wrong. We thought knowing "Solar time" would be more useful than in it, and we thought these "Leap seconds" would be less trouble than they are.
It's like you buy a cat to help with your rodent problem, figuring the cat will eat mice and isn't much trouble to look after, but after purchasing a cat you find that your problem was actually rats, your cat is terrified of these large dangerous creatures and sometimes gets bitten by them necessitating expensive vet bills and now you need to pay a lot of attention to the poor animal and also now need to buy cat food.
Heh, I like the analogy but my question was really why it was considered such a hassle.
I mean we deal with daylight saving time all the time and I know it's not the same because the leap second affects UTC, not just local time zone, it's just that you are either dealing with monotonically increasing time like epoch, or you are dealing with "human" time and I found no distinction in the latter.
Is it "just" that leap seconds or delay seconds caused problems in epoch to utc conversion? Note the just in quotes, but did I just answer my own question? :)
What does "technically legal" mean here, what authority is that coming from?
The co-ordinated universal time, UTC exists by international agreement. In the 1960s lots of countries signed a treaty so that's the "authority" AIUI.
The treaty says everybody agrees that this new standard will try to track "solar time" which felt intuitively reasonable. They want something equivalent to the old GMT which was really based on solar time, except more modern. At first the idea was, well, we just work out how fast this damp rock spins more precisely and we can use that to ensure everything works forever.
More precise measurements of the damp rock showed that, annoyingly, Mother Nature did not provide the spinning rock as a precise clock, it spins slower and faster according to a huge number of variables and so the best we can do is measure the spinning against an actual clock. So, "Leap seconds" were born to meet that legal requirement to have UTC match the solar time.
The "leap hour" would likewise fulfil this requirement, just in a deliberately useless way because we actually do not care about precisely tracking solar time. If we did, almost every human in the world would be perpetually annoyed because of course our present system of "time zones" means on average we're at least 30 minutes wrong!
Everybody agreed that "Leap seconds" are a sufficiently bad idea
No. Not everybody. I prefer accurate time, and all the complaints I've heard hold little water.
My servers need to timesync forwards and back all the time, eg timedrift. They need to jump to new times, or slowly drift, depending.
VMs can be hypervisor starved, or need to move to a new host.
Servers also need to handle missing time. Any daemon or program which cannot handle this is buggy, broken, and needs to deal.
Leap seconds are just part of all of this, and present no new issues compared to normal time change. I question the capabilities of any engineer who singles out time second as difficult to deal with, time is constantly changing on servers. Constantly.
So back to the start, no... everybody doesn't agree. Google isn't "everybody".
Accurate to what though, and for what? We decide what the standard is, and it seems like it would be a lot easier to have accurate time if we aren’t adding or subtracting seconds here or there. Does it really matter if the sun crests the horizon a second earlier than it did ten years ago? If it does, isn’t it much easier to just adjust your sun-cresting time?
> Russia needed time to update glassnoss satellites
GLONASS maybe? or really glasnost era satellites?
Glonass is correct. On mobile, thanks for the correction.
A butterfly flaps its wings in Tokyo and we lose a leap second.
> because Russia needed time to update glonass satellites.
Why is this? As leap seconds don’t occur on a regular frequency, I assume they are not hardcoded on the software or hardware on board, but the control centre uploads them on the satellites enough in advance once they have been scheduled. So why can’t the control centre just stop sending those updates?
My understanding the problem is that GLONASS is aware of leap seconds at all. It sends messages in UTC, which has this leap second funny business. GPS uses a special "GPS time" (sometimes abbreviated UT) that doesn't have a leap second. For further confusion, the leap second ensures that UTC is never more than 0.9 seconds off of mean solar time, aka UT1.
This type of assumption that was made early in a massive software and hardware project that's now been ossified for ~50 years is going to be hard to change.
Among other things, turbulent currents of liquid iron in the Earth's core can make the core drift eastward or westward, which causes the crust and mantle to turn slower or faster. Same thing with the strength of the jet stream.
See https://en.wikipedia.org/wiki/Leap_second#:~:text=Other%20co...
ELI5: How does this impact UNIX timestamps? Particularly for things that are in maintenance mode or otherwise minimally maintained.
Nothing I do requires this level of precision, but certainly there are things that do.
UNIX timestamps are fully ignorant of leap seconds, i.e. pretends they don't exist. That means there can be physical seconds of time that cannot be referenced with a UNIX timestamp (when a leap second is inserted) as well as UNIX timestamps for seconds that don't exist (when a leap second is deleted).
It also means that if you subtract two timestamps, you might not get the actual time between them. Though this is also true of most ways of representing time (TAI being a notable exception).
Whenever leap seconds were added, Google was running the clocks on their servers slower/faster over a longer period of time (hours) so they would slowly drift back in sync with the solid platinum, perfectly spherical grandfather's clock sitting in NIST or whatever: https://developers.google.com/time/smear
"To authorities responsible for the measurement and distribution of time" is just the best preamble ever.
The only better thing is the organization being called "International Earth Rotation Service"
Oh boy :) I think that would come with IERS Tax.
You have to go to the ends of the earth to cancel.
The real problem is finding the antipodal help desk without digging.
Someone should establish the Interplanetary Sun Orbiting Service.
>Someone should establish the Interplanetary Sun Orbiting Service.
I hope they have one of those logos with a bunch of weird freemason symbols that freak people out.
Sounds like something out of a Douglas Adams novel.
Or XKCD. I love patch day.
It’d fit right into Thief of Time by Pratchett - the monks literally measure and distribute time.
They should call themselves Time Lords
Traditionally, that was the email address for the NTP service at various organisations, in the same way that postmaster was for the mail service.
For those who need more context of who the Time Lords are
The Time Lords are a fictional ancient race of extraterrestrial people in the British science fiction television series Doctor Who. In-universe, they hail from the planet Gallifrey and are stated to have invented time travel technology.
https://en.wikipedia.org/wiki/Time_Lord
For further context, Doctor Who is a member of the species.
I think if we're being pedantic, the character's name is "The Doctor". The TV show is named "Doctor Who" but the character doesn't call themself that and a name is what something is called.
[Edited to avoid assigning a gender to a character who has had different genders]
And, I think, the last of them remaining.
The Master always comes back, of course. They're such perfect frenemies.
(Depends on the era of course, sometimes there are other timelords, sometimes not.)
"Director Earth Orientation Center of IERS Observatoire de Paris, France"
Even the titles are sci-fi.
“Time Lord” could have been used instead of Director. At least once. Please.
Being located in Paris, it would have to be "maître du temps".
Master of Time. One of the Masters of the Universe.
Maybe shorten it to Maître d'
For many years, the title of the leadership role over the various precise time products at the USNO was "Director of the Directorate of Time"
Do they have an insignia or patch? Can we buy it?
Planetary Defense Officer [1]
[1] https://en.wikipedia.org/wiki/Planetary_Defense_Coordination...
If the UTC-TAI offset remains at -37s, then it also means the UTC-GPS offset remains at -18s. TAI and GPS have a constant 19s offset from each system.
> The difference between Coordinated Universal Time UTC and the International Atomic Time TAI is :
>
> from 2017 January 1, 0h UTC, until further notice : UTC-TAI = -37s
This means the atomic clock is behind the solar clock by 37 seconds? I also don’t understand the reference to 2017.
> I also don’t understand the reference to 2017.
My guess is that is when they last changed the offset, so the -37s has been in effect since then.
Apparently December 2016 was the last time a leap second was inserted, at least that's what Wikipedia says:
https://en.wikipedia.org/wiki/Leap_second
we were ought to insert a negative leap second, but cowards got too afraid it would break code
> This means the atomic clock is behind the solar clock by 37 seconds?
If anything, it's the other way around.
A UTC day is defined as exactly 86400 SI seconds. But an actual mean solar day is a few milliseconds longer (although the difference is not constant due to irregularities in the Earth's rotation--but the average difference is expected to slowly increase over time). SI seconds are counted by atomic clocks, so UTC advances its day by one every 86400 atomic clock seconds.
But a solar clock that advances its day by one every time the mean sun reaches noon (it has to be the mean sun because the rate at which the actual sun moves across the sky varies over the course of a year, we need to look at the average) will advance its day a few milliseconds later than UTC does. Or, to put it another way, each time period that the solar clock says is exactly 86400 seconds, is a few milliseconds longer according to the atomic clock.
As this happens day after day, the difference accumulates, and when it gets close to being a full second, a leap second gets inserted into UTC, so that one of its days is 86401 seconds long instead of 86400. The reason for this is that UTC is not just counting atomic clock time; it also has to stay in sync with where the sun is in the sky since so many human activities are tied to that. And we humans have defined "in sync with the sun" to be "within a second of the average sun". In other words, we want UTC noon to be within a second of mean solar noon on the prime meridian.
So the 37 seconds is how far mean solar noon would be behind UTC noon, if we didn't use leap seconds--at UTC noon, the mean sun would be 37 seconds short of actually crossing the prime meridian in the sky.
"In other words, we want UTC noon to be within a second of mean solar noon on the prime meridian."
Why?
If I travel 1 mile east or west of the prime meridian, my solar noon now comes 2-3 seconds earlier/later. It's nearly impossible to have your local time match your local solar noon. For most of the population, solar noon is, on average, 30 minutes off of 12:00 noon.
Plus, solar noon varies from day to day by 10-20 seconds. Check the charts out. https://www.timeanddate.com/sun/usa/new-york
Probably there are things more important than your lunch that need time to be exactly synced with sun position
For things that need much more precusion than my lunch, ±1 second probably still isn't good enough, so they need another layer of correction anyway. Given that exists, might as well push leap seconds into that layer too.
> Why?
Um, because it's the prime meridian and that's how UTC is defined?
> It's nearly impossible to have your local time match your local solar noon.
Which is why I specified on the prime meridian, which is the particular local meridian that UTC is defined as corresponding to.
> solar noon varies from day to day by 10-20 seconds.
Which is why I was careful to specify mean solar noon.
I'm not quite sure what your issue is. Yes, we have time zones tied to specific meridians, and the actual sun's speed in the sky varies (which I mentioned in my post, so I'm not sure why you seem to think I'm unaware of it) so in most places local time by the clock doesn't match local time by the sun. Yes, a leap second adjustment to UTC is quite a bit smaller, taken in isolation, than the annual variation in actual solar time vs. mean solar time.
But over time, if we didn't have leap seconds, the difference would accumulate. The accumulated difference now between UTC and TAI is 37 seconds--which is almost twice the maximum variation in actual solar noon from mean solar noon that you refer to. We humans have collectively decided that we don't want that, and that it's better to do the adjustments a little at a time rather than in bigger lumps.
"But over time, if we didn't have leap seconds, the difference would accumulate. The accumulated difference now between UTC and TAI is 37 seconds--which is almost twice the maximum variation in actual solar noon from mean solar noon that you refer to."
No, the 10-15 seconds I mentioned is the daily variation in solar noon.
From the link I posted, in NYC, solar noon on 2026-01-01 is at 11:59am. On 2026-01-31, solar noon is at 12:09pm. In one month, it has drifted 10 minutes. That's much greater than the 37 leap seconds we have added in 60 years.
"We humans have collectively decided that we don't want that, and that it's better to do the adjustments a little at a time rather than in bigger lumps."
Yet we just reversed that decision. No more leap seconds after 2035. After trying it, we decided it was terrible.
> the 10-15 seconds I mentioned is the daily variation in solar noon.
Yes, but averaged over an entire year, it still comes out to zero. The difference between mean solar and atomic time does not. It accumulates over the years.
> we just reversed that decision
We paused it for 100 years after 2035. That doesn't change the physical fact that the Earth's rotation will continue to slow over the long term. We might eventually decide to just not care about that when it comes to civil timekeeping, but that's not what the decision you're referring to did. It just said we can afford to let the difference between UTC and TAI accumulate from 2035 to 2135 (by which time it is predicted to be about a minute) while we figure out what we want to do over the longer term.
Hear me out. We can just mount jet engines along the equator and rotate them 180 to gain or lose time. And then connect them to my snooze button.
The problem is future societies harvesting the engines for interstellar probes. This problem has been discussed in a series of books by Larry Niven.
There's a graphic novel by Cixin Liu "The Wandering Earth" where they not only stop Earth's rotation with this method, but also propel Earth out of the solar system (for what appear to be good reasons, I might add). Can't quite remember what fuel they used for the engines.
> for what appear to be good reasons, I might add
[Spoiler]
They are good reasons. Conspiracy theorists are able to persuade almost everybody that the reasons were bullshit, an excuse to seize power or something, and so the few who still insist this was necessary and mustn't stop are executed. Almost immediately after those executions, Mother Nature proves them right. So that leaves everybody: Guilty of having murdered their saviours and with no choice but to carry on with the very plan they had insisted was bogus...
There is a Chinese movie but I'm kinda surprised no Hollywood studio got themselves a rights deal and made a US-friendly movie where the Sun conveniently blows up slightly earlier and our heroes are vindicated and everybody agrees they were right all along.
IIRC they accelerated rock as the reaction mass. Gigatons of rock accelerated to well above escape velocity and launched from the ground.
In the real world their scheme is doomed as it would strip the atmosphere off of the Earth, but since they were planning to leave the solar system the atmosphere was going to freeze to a solid anyway so maybe it didn't really matter. To be honest I thought the entire scheme was an extremely elaborate cover for the fact the lead ship was the actual ark and everyone else was just plain doomed. This would have mirrored one of the themes in the 3 Body Problem where interstellar space travel is strictly forbidden until everybody can participate at once. The "launch the Earth as a spaceship" concept was so poorly thought out I thought it had to be a fraud in the story, and our somewhat dense protagonists just didn't catch on.
I feel like we can all just jump at the same time. I mean, we only need a second or two, right?
Well...we would all have to be at the same spot so that we don't cancel each other out. But that would come with its own challenges
https://what-if.xkcd.com/8/
(oh and it wouldn't be strong enough to affect the Earth's rotation)
Maybe a whole bunch of people can charter some planes, fill them with weight, and just travel full around the earth to where they started.
Wouldn't it just be easier to have Superman fly around the planet a bunch of times really fast to do the same thing? Then you wouldn't have to worry about having to deal with all of that engine maintenance.
It would appear that this has worked as they haven't had to insert leap seconds for quite a while.
No, jet engines push against the atmosphere and the atmosphere is a part of the earth
https://physics.stackexchange.com/questions/608372/if-a-jet-...
It would have to be rockets. My napkin says 2B starship boosters and 250K tons of propellant per second should give us around 1 second per year.
If the jet engines are pushing hard enough, then the atmosphere won't be a part of the earth for long.
Then we'll have to decrease the radius a bit.
You could actually move very large quantities of water around and probably have a measurable impact. Like draining the California central valley aquifer.
They should have a global holiday to celebrate the people who maintain time/date related code in OS kernels that keeps the world from imploding.
Lol. Exactly!
I like the argument that we should have 12 months that are exactly 30 days long, and then merge whatever is left into a single timeless holiday.
Yes, see also
https://en.wikipedia.org/wiki/French_Republican_calendar
Because of you I have learned the word 'intercalation', and am grateful for it.
https://en.wikipedia.org/wiki/Intercalation_(timekeeping)
There would be 5-6 days without time every years?
I've often dreamed of and revisited this idea. I first started thinking of it seriously when I realized I was paying the same rent in February as in January despite a significantly shorter-than-mean (30.4375) month...!
My ideal year is 12 months, each 5 weeks long, each week 6 days long. At the summer solstice, 3 intercalary days (bank holidays), at the winter solstice, 2 or 3 intercalary days depending on leap year.
Sure thing Charles-Gilbert Romme.
I thought it was 13 months exactly 4 weeks long, which takes us to exactly 364 days
We could call the 13th month "Undecember"
Lol the Kernel is "easy" it's userspace and distributed systems that are a b*tch
What happens to systems such as Spanner under these circumstances?
Is it a headache or a non-issue
Leap seconds are not added on a regular schedule like leap days, they depend on physical measurements of Earth. So high reliability systems with comprehensive timekeeping would not be perturbed by these choices, I would think.
It’s a huge problem. The most common approach to address it is called smearing; the duration of each second for a 24 hour period ahead of the “leap” is adjusted. For strict ordering systems this works as each device maintains time sync with the global clock, the duration of a clock cycle is just slightly different. I think this was in the original Spanner paper, actually.
Some rare systems use monotonic oscillator seconds and ignore the earth rotation second, but if you ever have to translate those to real time, you get an accumulating disaster over time and it’s generally regarded as not a good idea.
I wonder if that's what electricity producers do? If you are selling 50 or 60 Hz service, an extra second here or there must really mess things up.
Clocks used to be able to use the 60Hz cycle to track time, and grid providers would run slightly slow or fast ("time error correction") to get back into sync. A leap second would just be part of this.
I believe in the US this error correction has been discontinued in the East and in Texas, but is still done in the West for some kind of non-clock "inadvertent interchange" reasons I don't understand.
Wait is that why my oven and microwave clocks are constantly getting out of sync by multiple minutes every year?
Out of sync with each other, or are they drifting together in lockstep? In the latter case, yes, that's the most likely explanation.
A few years ago, a dispute between Kosovo and Serbia caused the entire European grid to drift away from 50.000Hz down to 49.996Hz. Millions of microwave clocks across the continent ended up 6 minutes late: https://hackaday.com/2018/03/09/europe-loses-six-minutes-due....
The real Time Variance Authority
My longevity will extend one second into the future in nominal terms, increasing the chance to reach the 22nd century a tiny bit.
I enjoy how Chrome asks me if I want to auto translate from German to English. Where did it get German from? It's French!
It's a mix of french and english... so it's german.
A mix of English and French is just called... English
Frenglish
Franglais?
This book would probably disagree :-) https://www.fnac.com/a19325120/Bernard-Cerquiglini-La-langue...
Probably from the "Content-Language: de" header
Ok but that makes even less sense
According to Wikipedia [0] the headquarters of IERS (International Earth Rotation and Reference Systems Service) is in Frankfurt, Germany (contact information on their website [1] has an address in Frankfurt too). The web server hosting the linked file also contains German text in its error page:
> Dieser URL wird nicht beantwortet. Bitte wenden Sie sich mit Ihrer Anfrage an das Bundesamt fuer Kartographie und Geodaesie.
[0] https://en.wikipedia.org/wiki/International_Earth_Rotation_a...
[1] https://www.iers.org
As one HN comment said years ago: I feel leap seconds have always lived in the wrong abstraction layer.
They should live in the same abstraction layer that does leap days and daylight savings: the time zones.
Leap days, February 29th, are not at the level of time zones. Different time zones do not disagree as to when March 1st will occurs immediately after February 28th.
god that would be awful. Can you imagine time zones being one second off from each other. Or two or three? ah yes, india is GMT+4:30:03, where europe is GMT+0:59:58
The TZDB could handle it though
https://m.xkcd.com/2867/
I had not seen that. In the nineties I worked on an alerts system where you could sign up for like some sport or weather data at a certain time of day. We stored the alert times as minutes before midnight and then ran the time to trigger calculations often enough that unless you were some freak that wants weather alerts at 2 am it basically worked to send one alert each day at the appropriate time; we had a special non-OS copy of the tzdb as the users were global. One quarter I forgot to update it and everyone in Mexico City got their alerts one hour off till someone complained and I updated it. We also had data feed alerts, like score changed or stock hit x% over previous high, where the problem is some data is manually entered and can be off by a factor or two of ten from time to time. Had to be filtered. I had a lot of fun.
Already a thing between UTC and TAI.
Right, and orders of magnitude more people have to deal with UTC and timezones compared to TAI and the offset. So it's good to have it in the layer that it's in
The changes in Earth's rotational speed that leap seconds help account for affect the whole globe. Why shouldn't the effects be noted in the global time standard?
Same with leap days though?
The point is that it's weird that we handle a day every 4 years off in a different way to a couple of second being off.
Don't we handle them mostly the same? In a leap year, the month of February gets a 29th day, labeled 29. On a leap second, one of the minutes gets a 61st second, labeled 60. Or we drop the 60th second, and second 58 is followed by second 00 of the next minute.
The notable differences are that
1) the leap second happens at the same time globally (23:59:60 UTC), while leap days start at 00:00 local time
2) leap seconds happen at irregular intervals
3) leap seconds are nearly universally implemented wrong, because the ability to show :60 on a second display for for one second at most twice per year is just not worth the implementation complexity
You could argue about 1, but the alternative would lead to much more complicated timezone math (time zones can be an additional one second apart from each other depending on whether the leap second is already applied) for very limited benefit. Number 2 seems unavoidable, and 3 is entirely unintended, just the way things have worked out in real life
Leap days are predictable whereas leap seconds are not.
The leap day system handles the mean, the leap seconds handle the variance around the mean. The need for leap seconds is not predictable—they zero out accumulated error.
That would create much more chaos, because every region autonomously decides on its timezone(s). You'd have different countries and/or timezones using different leap second counts.
Yes! I yearn for the day when central daylight savings time is 1:00:00:36 behind eastern time, but standard central time remains offset by 1 hour exactly (except for leap years, which are obviously 1:00:00:36 offset all year round).
Does this mean the negative leap second isn't happening anymore?
Not anymore forever. We’re just not adding one for this year. We might need one next year, we might not. It all depends on the Earth’s rotation and orbit
and Earth's rotation was too fast for last several years
we were all waiting for the negative leap second to finally happen - but cowards got too afraid
I don't think it's cowardice, is it? The graph at https://en.wikipedia.org/wiki/Leap_second seems to indicate that adding a negative leap second at this point in time would be improper. (We're ~+0.1s off, and a negative leap second would occur if the line was approaching +0.6s. I'd like one too just for the curiosity of the thing, but … the Earth isn't having it.)
There's an opportunity to insert or remove a leap second twice a year. They only decide about 6 months in advance of each opportunity what to do (leap second, skipped second, or do nothing).
This announcement is very much a nothing burger; it’s already been more or less decided that adding leap seconds just isn’t going to be a thing anymore (in our lifetime). Here’s on article from 2022: https://www.timeanddate.com/news/astronomy/end-of-leap-secon...
World will end at 26 December so no leap second needed
Cool, I don't have to set my clocks back this December.
Notice they only said leap second.
Meanwhile....
International timekeepers to vote on changing the leap second to a leap hour
https://www.scientificamerican.com/article/international-tim... (https://archive.ph/GnQUj https://news.ycombinator.com/item?id=48842329)
really, my I just don't have the time to keep up with this.
We can change that!
A leap hour wouldn't affect you.
In practice it will never affect anyone because it's a legal fiction, but even if you pretend to believe we would actually introduce this "leap hour" it would be in the distant future long after we're all dead and if there are still humans who have any idea the year 2026 happened they're not sure which of Donald Trump, Taylor Swift, Tony Stark and John McClane were real people.
Edited to add:
This is such a ridiculously long time frame that they might not be sure whether we were worried about climate change, for them that's either a disaster they survived (and maybe most didn't) or it's a weird blip in their historical charts which they struggle to explain. Did our civilisation do something very, very stupid? There is a flammable gas deep underground, did we set fire to it because we were crazy? Why the hell would we have done that? There are signs we deliberately set fire to the coal which is a toxic rock also found underground? That would explain the global climate going nuts. Maybe it was a ritual or something. Ancient people are mad.
Up until now we have added 1 leap second every 2 year (27 leap seconds since 1972). So if it continues like this, in 7200 years it would be 1 whole hour, and in "only" 3602 years it will be closer to the next hour than the previous (so a natural time to add the leap hour).