#leapseconds
Live, measured metrics for the hashtag #leapseconds from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #leapseconds
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 09:51 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 09:51 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:51 UTCEverything below is measured over the latest 16 public posts (spanning ~52537 hours).
Posting hours (UTC) — busiest: 23:00
Languages: English (15) · German (1)
Avg boosts / post: 0.3
Top of the latest posts
Just read that the International Earth Rotation and Reference Systems Service (IERS) is officially abandoning/abolishing #LeapSeconds by the year 2035, because they are just so disruptive to computer systems. Tell me you can't get a handle
You might have heard, that CGPM will vote on whether to (de facto) abolish leapseconds in October, due to the technical problems it causes, each time we have a leapsecond. And because of the prospect of the first ever negative leapsecond. h
I wrote a post about recent news on the subject of time. Just when you thought that all you had to have programming indigestion about was time zones: https://www.beflagrant.com/blog/time-roundup-2024-04-08 #LeapSeconds #LunarTime
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/leapseconds