#corememory
Live, measured metrics for the hashtag #corememory from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #corememory
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-27 12:34 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-27 12:34 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:34 UTCEverything below is measured over the latest 40 public posts (spanning ~30487 hours).
Posting hours (UTC) — busiest: 04:00
Languages: English (33) · Portuguese (3) · German (2) · French (1)
Avg boosts / post: 0.9
Top of the latest posts
Thanks to a book recommendation by @bert_hubert [1], I went on a tangent learning more about the absolutely fascinating history and workings of core memory (and core rope memory, its read-only version). Some of this also very interesting fo
MUDs and the ability to reload new server without dropping connections (a “hotboot”)… https://boston.conman.org/2025/02/11.2 …reminded me of an old RSX-11M application from an aeon ago, running part of a state government. The app was too bi
Happy with how my mounting / framing of this core memory module turned-out. Beautiful as a historical display piece, and I wouldn't mind trying to connect it to an Arduino some day. Addressing memory to read/write one bit of data at a time
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/corememory