#j1a
Live, measured metrics for the hashtag #j1a from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #j1a
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-27 14:25 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-27 14:25 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-07-27 14:25 UTCEverything below is measured over the latest 2 public posts (spanning ~23451 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 2
Top of the latest posts
Between Charley Shattuck's #myforth on the #8051 (8-bit) and James Bowman's #SwapForth on his #J1a (16-bit FPGA softcore) and GreenArray's #arrayforth on the #GA144 (144 self-contained computers on a chip) and FORTH Inc's #SwiftX (#MSP430 a
I am very curious about large numbers of small #Forth computers running on an #fpga together. #j1 #j1a.#verilog What should I be reading about?
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/j1a