#nascom2
Live, measured metrics for the hashtag #nascom2 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #nascom2
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 20:51 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 20:51 UTCNo related tags with measured usage found for #nascom2.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 20:51 UTCEverything below is measured over the latest 8 public posts (spanning ~15918 hours).
Posting hours (UTC)
Languages: English (7) · German (1)
Avg boosts / post: 0
Used together with
Top of the latest posts
Because I have an odd sense of humor, I implemented Chacha20 in BLS Pascal on the Nascom2, running in my browser (https://tommythorn.github.io/virtual-nascom/virtual-nascom.html) Turns out adding 2 32-bit values is really painful this way.
For CP/M, the #Nascom2 only had one major flaw: a 48x16 resolution. It's been another 40 yo project to find the cheapest/simplest way to modify the existing video interface for something closer to 80x24 (alas, loosing all SW compatability i
It's unphantomable how much more useful my #Nascom2 would have been with CP/M; the SW library would be orders of magnitude larger and obs. floppy is incomparably more convenient than tape. I have lost major projects to tape read errors and
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/nascom2