#i8086
Live, measured metrics for the hashtag #i8086 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #i8086
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 23:11 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 23:11 UTCNo related tags with measured usage found for #i8086.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 23:11 UTCEverything below is measured over the latest 10 public posts (spanning ~24976 hours).
Posting hours (UTC)
Languages: English (4) · German (3) · Russian (2) · Dutch (1)
Avg boosts / post: 2
Top of the latest posts
Awesome book. #Assembly #ASM #x86 #i8086
I've some #fujitsu #i8088 #i8086 #cpus and i'm wondering why they habe a gab inside the case? Can someone explain it? #retrocomputing #retrocomputer
After adding the missing size check, #LuaLang behavior is much more benign. A 64K segment size limit on table sizes isn't ideal, but it beats a hard crash, and it's a stable jumping-off point for further modifications. #retrocomputing #msdo
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/i8086