#openmsxdebugger
Live, measured metrics for the hashtag #openmsxdebugger from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #openmsxdebugger
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 09:47 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 09:47 UTCNo related tags with measured usage found for #openmsxdebugger.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:47 UTCEverything below is measured over the latest 7 public posts (spanning ~11432 hours).
Posting hours (UTC)
Languages: English (7)
Avg boosts / post: 0
Top of the latest posts
My next idea improving OpenMSX is a simple code analyser widget: https://github.com/openMSX/openMSX/pull/1707 #debug #openmsxDebugger #gamedev #openmsx #msx #emulation
Here is an idea that I think is useful: ability to disassemble any Tcl string that you want, not only the stuff from main memory. #openmsx #openmsxDebugger #msx #z80
Along with PR #1709, I guess the basic features of the debugger are close to complete. https://github.com/openMSX/openMSX/pull/1710 #openMSX #openmsxDebugger #msx #debugger
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/openmsxdebugger