#timeclock
Live, measured metrics for the hashtag #timeclock from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #timeclock
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 16:41 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 16:41 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 16:41 UTCEverything below is measured over the latest 13 public posts (spanning ~35113 hours).
Posting hours (UTC) — busiest: 14:00
Languages: English (13)
Avg boosts / post: 0.5
Top of the latest posts
#annextimelog is progressing nicely. It can now: - track (overlapping!) events with arbitrary metadata (title, location, note, tags, arbitrary other fields) - semi-intelligent time parsing (e.g. easy 'yesterday' reference with y10:00) 🎉 fi
Finishing the day with the most basic feature a time tracker can possibly have: recording a period of time. ⏱️ This is #annextimelog, the :gitannex: #gitAnnex based time tracker I'm making in the hope that it'll suit me better than #timewar
Couldn't find a way to export #timewarrior files to the #timeclock format for #PlainTextAccounting...so I made my own 😇 https://git.disroot.org/badrihippo/timewarrior-timeclock
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/timeclock