#gnomeClocks
Live, measured metrics for the hashtag #gnomeClocks from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #gnomeclocks
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-28 08:50 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-28 08:50 UTCNo related tags with measured usage found for #gnomeclocks.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 08:50 UTCEverything below is measured over the latest 5 public posts (spanning ~26880 hours).
Posting hours (UTC)
Languages: English (3) · German (2)
Avg boosts / post: 8.8
Top of the latest posts
Not much news on other mobile platforms but I needed a reliable clock that wakes me up even when the 📱 is suspended so I added some boottime clock support to #gnomeClocks. This together with #feedbackd support can be found in https://gitla
Another day out with #phosh and the #OP6 - Woke up with #gnomeClocks ⏰ - Looked up the address of the 🍟 via #Firefox and its mobile config - picked my way via #puremap's offline map feature - Send #SMS via #Chatty - Replied a toot via #tub
@craftyguy @alf @linmob @tuxdevices @postmarketOS Currently I'm running "20221123-0638-postmarketOS-v22.06-phosh-18-purism-librem5-installer.img.xz" -- "megapixels-purism" wasn't working and other than that I'm systematically going through
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/gnomeclocks