#time_t

Live, measured metrics for the hashtag #time_t from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #time_t

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.

$520.70/ year · 6-character #name
Claim #time_t — $520.70/yr→
Annual, renews each year
Buy on hashtag.space (web3)
one-timepay once, yours for life
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
28
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 28
0.4
Avg reactions / post
Mastodon · last 28

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 09:01 UTC
0
07-21
0
07-22
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27

0 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:01 UTC
#L33tTime
0 uses · 0 accounts / 7d
#64bit_time_t
0 uses · 0 accounts / 7d
#time64_t
0 uses · 0 accounts / 7d

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:01 UTC

Everything below is measured over the latest 28 public posts (spanning ~15571 hours).

Posting hours (UTC) — busiest: 13:00

00:0012:0023:00

Languages: English (16) · Polish (8) · Chinese (2) · German (1) · Russian (1)

Avg boosts / post: 4

Top of the latest posts

  • whoa! I run a mix of debian testing/unstable on my main home machine and the "t64" packages have started showing up in unstable. I was like... "what's t64". And it's time. time is changing. https://lwn.net/Articles/938149/ #debian #time_t #

    lambdageek@[email protected]♥ 3↻ 752024-03-02 01:33 UTCView post →

  • 👉 Neuer Blog: „time_t Cast Away: Bits über Bord und der Y2K38 Bug ist zurück“ Die Umstellung auf 64-Bit-time_t gilt als Lösung für das Year 2038 Problem. Doch Direct Casts machen den Fix schnell unwirksam – und schicken uns zurück ins Jahr

    BEOZ@[email protected]♥ 2↻ 02025-08-24 16:35 UTCView post →

  • Yesterday, while testing time64, I was wondering if we could switch #Python to 64-bit #time_t immediately and unconditionally, and get rid of some #y2k38 problems we're facing today already (these affecting Python packages). Unfortunately,

    Jesus Michał von Gentoo 🏔 (he)@[email protected]♥ 2↻ 12024-10-05 06:38 UTCView post →

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/time_t