#i8008
Live, measured metrics for the hashtag #i8008 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #i8008
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 11: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 11:11 UTCNo related tags with measured usage found for #i8008.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 11:11 UTCEverything below is measured over the latest 3 public posts (spanning ~11081 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0
Used together with
Top of the latest posts
What's the main challenge in assembling old code on a modern(ish) assembler? The old assemblers only consider the first few letters of a mnemonic significant. The 8008 has an INC opcode. My assembler has an INCLUDE directive. (The old code
The 8008 assembler on the other hand requires some gymnastics to deal with a 16-bit label. The \HB\ prefix is specifying the high byte of the address. Note also, at lest in this codebase, there are no labels for data storage areas. The high
Looking again at my breadboard #i8008 project. I need to ensure the READY and INT signals are only generated at the right times, and probably the same with bus pull-ups (required for the faster 8008-1). I'm looking at the reference schemati
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/i8008