#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.

hashtag.org network · sponsored

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.

$5.00/ year · 14-character #name
Claim #locationlabels — $5.00/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
8
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 8
0.3
Avg reactions / post
Mastodon · last 8
—
Reddit posts / month
Reddit search
—
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · mastodon.social (Mastodon public tags API) · fetched 2026-10-03 03:36 UTC
0
09-27
0
09-28
0
09-29
0
09-30
0
10-01
0
10-02
0
10-03

0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.

Related hashtags

measured · mastodon.social (Mastodon public search API) · fetched 2026-10-03 03:36 UTC

No related tags with measured usage found for #locationlabels.

Live pulse

measured · mastodon.social (Mastodon tag timeline) · fetched 2026-10-03 03:36 UTC

Everything below is measured over the latest 8 public posts (spanning ~761 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: English (8)

Avg boosts / post: 0

Top of the latest posts

  • @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)

    LaPingvino 🟙 :ir:@[email protected]♥ 1↻ 02023-01-09 00:04 UTCView post →

  • @jeroenclemens this is the kind of thing for which I want to make #LocationLabels a thing :)

    LaPingvino 🟙 :ir:@[email protected]♥ 1↻ 02022-12-21 23:05 UTCView post →

  • @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

    LaPingvino 🟙 :ir:@[email protected]♥ 0↻ 02023-01-22 15:08 UTCView post →

#locationlabels across platforms

every network with a public tag surface

Follow #locationlabels straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.

X (Twitter) ↗Instagram ↗TikTok ↗Facebook ↗LinkedIn ↗YouTube ↗Threads ↗Bluesky ↗Mastodon ↗Reddit ↗Pinterest ↗Tumblr ↗

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