#timewarrior
Live, measured metrics for the hashtag #timewarrior from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #timewarrior
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 13:01 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 13:01 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 13:01 UTCEverything below is measured over the latest 40 public posts (spanning ~21770 hours).
Posting hours (UTC) — busiest: 18:00
Languages: English (38) · German (2)
Avg boosts / post: 0.3
Top of the latest posts
1½ years later, ⏱️ #annextimelog¹ exists and I use it daily to track things I do/work. Even simultaneous things, one of the key features I was missing in most other #FOSS #plainText time trackers such as #timewarrior or :hledger: #hledger.
#annextimelog v0.5.0 brings several improvements here and there and #timewarrior-style time range specification, e.g. > atl tr 15:00 - 10min ago work @home > atl tr 6h ago until now coding @workplace https://pypi.org/project/annextimelog/0.
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/timewarrior