#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.
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.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 02:41 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 02:41 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 02:41 UTCEverything below is measured over the latest 3 public posts (spanning ~213 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.3
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.
@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
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
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