#1b12

Live, measured metrics for the hashtag #1b12 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 #1b12

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.

$2,449.80/ year · 4-character #name
Claim #1b12 — $2,449.80/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
9
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 9
0
Avg reactions / post
Mastodon · last 9
—
Reddit posts / month
Reddit search
—
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · mastodon.online (Mastodon public tags API) · fetched 2026-11-04 00:21 UTC
0
10-29
0
10-30
0
10-31
0
11-01
0
11-02
0
11-03
0
11-04

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.online (Mastodon public search API) · fetched 2026-11-04 00:21 UTC
#ffd08df1b12
4 uses · 2 accounts / 7d
#a1ad12b9f1e
0 uses · 0 accounts / 7d
#a9ea56b1c12
0 uses · 0 accounts / 7d
#b1kr12
0 uses · 0 accounts / 7d
#f1a614b4b12
0 uses · 0 accounts / 7d
#1ce12b
0 uses · 0 accounts / 7d
#1B12D0
0 uses · 0 accounts / 7d
#12b4b1
0 uses · 0 accounts / 7d
#F1B12D
0 uses · 0 accounts / 7d
#1B0D12
0 uses · 0 accounts / 7d
#1BB12B
0 uses · 0 accounts / 7d
#1B12F7
0 uses · 0 accounts / 7d

Live pulse

measured · mastodon.online (Mastodon tag timeline) · fetched 2026-11-04 00:21 UTC

Everything below is measured over the latest 9 public posts (spanning ~16045 hours).

Posting hours (UTC)

00:0012:0023:00

Avg boosts / post: 3.2

Top of the latest posts

  • Federated private groups (Announce vs Add) @[email protected] mentioned in another thread that the way Hubzilla and threadiverse software handle group discussions is incompatible. It got me thinking about whether that is true. At its core both

    julian@[email protected]♥ 0↻ 72026-02-15 15:59 UTCView post →

  • More reliably federating microblog responses I encountered an odd federation issue where microblog responses do not get reliably federated to threadiverse instances. Example: A user on threadiA instance makes a new post to a category/commun

    julian@[email protected]♥ 0↻ 52025-10-15 16:45 UTCView post →

  • Moving topics/contexts from one community to another At Piefed office hours, @[email protected] and I got to talking about what's next for Piefed and the Threadiverse WG. One of those things is moving stuff between communities (or in bbs p

    julian@[email protected]♥ 0↻ 52025-09-26 03:57 UTCView post →

#1b12 across platforms

every network with a public tag surface

Follow #1b12 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/1b12