#y2k38bug
Live, measured metrics for the hashtag #y2k38bug from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #y2k38bug
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 05:49 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 05:49 UTCNo related tags with measured usage found for #y2k38bug.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:49 UTCEverything below is measured over the latest 3 public posts (spanning ~29661 hours).
Posting hours (UTC)
Languages: English (2) · German (1)
Avg boosts / post: 0.7
Top of the latest posts
In knapp 14 Jahren! Die #Epochalypse technisch erklärt. #y2k38 #y2k38bug #Y2038 #y2038bug Was ist der Y2k38 Bug? Eine technische Erklärung. - https://beoz.ch/was-ist-der-y2k38-bug-eine-technische-erklaerung/
Damn heliocentrists measure years like some pastoral nomads (nothing wrong with those though) while what we actualky ought to do is measuring periods of seconds which fit into common four byte int storage. #y2k38bug
I'm looking forward to the #y2k38 craze of the period leading up to #2038. Was it just #1999 and the first weeks of #2000 when the general populace was concerned about the #y2kBug aka the #milleniumBug? Or did it worry people for longer tha
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/y2k38bug