#losthours
Live, measured metrics for the hashtag #losthours from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #losthours
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 14:47 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 14:47 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 14:47 UTCEverything below is measured over the latest 2 public posts (spanning ~13943 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Used together with
Top of the latest posts
OK, traefik is really finicky with what configuration it reads from where and how much error it gives with regard to the configuration files. If I include a `traefik.yaml` file with the endpoints and some other configurations, it reads it,
😭 Devastated! Word crashed and I lost a 6000-word file I spent 7 hours editing! 😩💔 Can't believe all that hard work vanished in an instant. Learn from my mistake, folks: always save and back up your work regularly! 😫 #WordCrash #LostHou
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/losthours