#f37d

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

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 #f37d — $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
3
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 3
0
Avg reactions / post
Mastodon · last 3
—
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-01 15:05 UTC
0
09-25
0
09-26
0
09-27
0
09-28
0
09-29
0
09-30
0
10-01

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-01 15:05 UTC

No related tags with measured usage found for #f37d.

Live pulse

measured · mastodon.social (Mastodon tag timeline) · fetched 2026-10-01 15:05 UTC

Everything below is measured over the latest 3 public posts (spanning ~213 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: English (3)

Avg boosts / post: 0.3

Used together with

#2f ×2#c01e ×1#msx ×1

Top of the latest posts

  • @spacemoai MSXTurboR, DOS1 Anyway I've managed to make it work with PHYDIO. The problem happens only with #f37d + #2f call.

    MSXWiki@[email protected]♥ 0↻ 02023-05-17 10:14 UTCView post →

  • @spacemoai I can read the first 9 sectors. The 10th reads a different one (like if the system believed it's a 2DD disk and was accessing the other "side"). However, the same .DSK image with the same machine (OpenMSX emulating an A1GT) has a

    MSXWiki@[email protected]♥ 0↻ 02023-05-08 21:37 UTCView post →

  • I'm having issues with a #MSX disk reading routine. If a use DSKI$ from the BASIC, I get what I expect. But if I use the BDOS call (through #F37D) I read a different sector of the disk (even if the logical sector number is the same in both

    MSXWiki@[email protected]♥ 0↻ 12023-05-08 13:24 UTCView post →

#f37d across platforms

every network with a public tag surface

Follow #f37d 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/f37d