#slashem
Live, measured metrics for the hashtag #slashem from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #slashem
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 19:56 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 19:56 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 19:56 UTCEverything below is measured over the latest 9 public posts (spanning ~32517 hours).
Posting hours (UTC)
Languages: Spanish (4)
Avg boosts / post: 0.2
Top of the latest posts
Ok, lets crosscompile a small #NetBSD kernel for #VAX under #simh, I need every cycle for #slashem under my underpowered netbook. No, I wont use my netbook for it, but some amd64 machine there.
First I used to play as Doppleganger Monk in #Slashem, (the most known #nethack fork, you know, a #roguelike) somehow mirroring in-game fights from RL as a free software techie. Virtual kicks against mons, easy mode, with weird #tecniques f
#Nethack and #slashem being playable under #m68k 67020 cpu's and 4MB it's still impressive. Before someone replies me with ' #UltimaIV was more complex'... Nethack's/Slashem object/mon/env interaction it's far deeper even if the world and q
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/slashem