#locationlabels
Live, measured metrics for the hashtag #locationlabels from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #locationlabels
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 · mastodon.online (Mastodon public tags API) · fetched 2026-07-28 00:10 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-07-28 00:10 UTCNo related tags with measured usage found for #locationlabels.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-07-28 00:10 UTCEverything below is measured over the latest 8 public posts (spanning ~761 hours).
Posting hours (UTC)
Languages: English (8)
Avg boosts / post: 0
Top of the latest posts
@jpreisendoerfer @factotum I know it's not trivial, which is part of why I use the more or less neighborhood precision of the #LocationLabels to do a rough match on a meaningful level, as in you can match things to be close enough and weed
@helge @factotum @jpreisendoerfer also it's important to understand that the #LocationLabels use a region instead of a point, to guarantee searchability and privacy. if this is not implemented in the location property, it's by all intents a
@hrefna I implemented #LocationLabels using #UlamSpirals, for which I used the #OEIS to find an algorithm to iterate over the spiral (implemented at whenwhere.cf)
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/locationlabels