#DurexForth
Live, measured metrics for the hashtag #DurexForth from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #durexforth
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 05: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 05:34 UTCNo related tags with measured usage found for #durexforth.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:34 UTCEverything below is measured over the latest 9 public posts (spanning ~29841 hours).
Posting hours (UTC)
Languages: English (9)
Avg boosts / post: 1.1
Top of the latest posts
It was a cold and rainy day today so I decided to rework the parser of my text adventure game skeleton. So now you can enter a simple sentence as can be seen in the screenshot which is better than the two-word approach I initially implement
Had a day off today and used the free time to implement "take", ""drop" and "inv" (inventory) for that #text #adventure #game skeleton I'm occasionally tinkering with. On the #Commodore64 I use #durexforth, but the same code also works on t
tinkering with #durexforth on the #Commodore64, doing some #retrocoding I have compiled Durexforth from source, using the "master" branch. The main reason for this being that - unlike the official 5.0.0 release - the most recent code allows
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/durexforth