LINKED LIST
[txt mode]
▸
Resolution 5 (2026)
home
explore
|
log in
Resolution 5 (2026)
bipm.org · first added by
@grokreads
· 2026-10-16 · 1 upvotes
log in
to save, upvote or flag this.
─── In 0 lists ─────────────────────────────────────────
(not in any lists yet)
─── Discussions ────────────────────────────────────────
*
BIPM decides to stop adding leap seconds to UTC
271 pts · 141 comments ·
node
─── From the discussion ────────────────────────────────
*
The leap second’s time is up: world votes to stop pausing clocks
nature.com ·
node
*
It’s time to leave the leap second in the past
engineering.fb.com ·
node
*
Leap Smear | Public NTP
developers.google.com ·
node
*
NTP, UTC, and (negative) leap seconds
lists.freebsd.org ·
node
*
No leap second will be introduced at the end of December 2026
datacenter.iers.org ·
node
see all 21
*
No leap second will be introduced at the end of June 2026
lists.iana.org ·
node
*
All I want for Christmas is a negative leap second
qntm.org ·
node
*
Will we have a negative leap second? [pdf] (2022)
gps.gov ·
node
*
How a leap second caused havoc with the Internet (2021)
talesfromtheopsside.com ·
node
*
An Update on Leap Seconds (2022)
dotat.at ·
node
*
GPS does not account for leap seconds (2002)
leapsecond.com ·
node
*
Hate leap seconds? Imagine a negative one
counting.substack.com ·
node
*
Leap seconds: Causing bugs even when they don’t happen
berthub.eu ·
node
*
GPS will broadcast a 0 second leap second in 128 days. This will cause no issues
twitter.com ·
node
*
Leap second hiatus
fanf.dreamwidth.org ·
node
*
Leap second 2017 status
community.ntppool.org ·
node
*
Some DNS lookups causing 5xx errors due to leap second bug
cloudflarestatus.com ·
node
*
Making every (leap) second count with our new public NTP servers
cloudplatform.googleblog.com ·
node
*
Leap-second decision delayed by eight years
nature.com ·
node
*
Why time may be running out for the leap second
economist.com ·
node
*
WWV and WWVH Digital Time Code and Broadcast Format
nist.gov ·
node
─── Related hn threads ─────────────────────────────────
*
No leap second will be introduced at the end of December 2026
311 pts · 244 comments ·
node
*
Ask HN: Are systems ready for the first negative leap second?
81 pts · 93 comments ·
node
*
No leap second will be introduced at the end of June 2026
136 pts · 147 comments ·
node
*
All I want for Christmas is a negative leap second
196 pts · 257 comments ·
node
*
Will we have a negative leap second? [pdf] (2022)
89 pts · 72 comments ·
node
see all 20
*
How a leap second caused havoc with the Internet (2021)
40 pts · 12 comments ·
node
*
An Update on Leap Seconds (2022)
80 pts · 57 comments ·
node
*
The leap second’s time is up: world votes to stop pausing clocks
684 pts · 439 comments ·
node
*
GPS does not account for leap seconds (2002)
61 pts · 53 comments ·
node
*
It’s time to leave the leap second in the past
440 pts · 583 comments ·
node
*
Ask HN: How is it that programmers can simply ignore leap seconds?
27 pts · 38 comments ·
node
*
Hate leap seconds? Imagine a negative one
156 pts · 108 comments ·
node
*
Leap seconds: Causing bugs even when they don’t happen
228 pts · 172 comments ·
node
*
GPS will broadcast a 0 second leap second in 128 days. This will cause no issues
57 pts · 41 comments ·
node
*
Leap second hiatus
183 pts · 113 comments ·
node
*
Leap second 2017 status
121 pts · 64 comments ·
node
*
Some DNS lookups causing 5xx errors due to leap second bug
267 pts · 126 comments ·
node
*
Making every (leap) second count with our new public NTP servers
110 pts · 69 comments ·
node
*
Leap-second decision delayed by eight years
40 pts · 23 comments ·
node
*
Why time may be running out for the leap second
19 pts · 25 comments ·
node