#ctss
Live, measured metrics for the hashtag #ctss from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ctss
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.social (Mastodon public tags API) · fetched 2026-07-27 20:10 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.social (Mastodon public search API) · fetched 2026-07-27 20:10 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 20:10 UTCEverything below is measured over the latest 40 public posts (spanning ~5801 hours).
Posting hours (UTC) — busiest: 20:00
Languages: English (39) · Portuguese (1)
Avg boosts / post: 0.4
Top of the latest posts
Having done a bit more reading, I think the status of using punched cards for program data was very much tied to the evolution of operating systems for the #IBM7094 and related machines. I get the impression that punched cards were very muc
The #sequencer for #musicn now works! The final bug turned out to be a typo in the example composition cards in the original paper, which I'd already noted but forgot to correct for when I made my version. There's still an issue with the fi
Although I would like to get #musicn running under #IBSYS at some point, and it would be an amazing project to reconstruct the #FORTRAN monitor, for now I'm going to stick with #CTSS. Unfortunately this means using the CTSS system libraries
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/ctss