#TAsm
Live, measured metrics for the hashtag #TAsm from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tasm
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 14: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 14:47 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 14:47 UTCEverything below is measured over the latest 11 public posts (spanning ~39705 hours).
Posting hours (UTC)
Languages: English (10) · German (1)
Avg boosts / post: 0.7
Top of the latest posts
And that's the .ASM and .ING files done! https://codeberg.org/thelastpsion/ctran/commit/dbc50dbdab0e14cef1ecc4b1391dcada0f54b59e There are other issues with #TASM file generation in my code, such as class property generation. Thing is, I th
New issue, still #TASM-related. Almost certainly a bug in Psion's #CTRAN that I feel I need to resolve. This line in C struct UNDOMAN: VOID * pEngine; Gets translated into TASM code like this: Undoman pEngine dw ? But this: VOID* pEngine; T
Has anyone got any tips on converting #TASM and #MASM code to a more modern assembler like #NASM? Even just between TASM and MASM would be helpful. I've got a few old bits of #Psion 8086 assembly that I'd like to use with NASM. My aim is to
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/tasm