#wordexp
Live, measured metrics for the hashtag #wordexp from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #wordexp
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-09-29 05:23 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-09-29 05:23 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-29 05:23 UTCEverything below is measured over the latest 3 public posts (spanning ~0.6 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.7
Used together with
Top of the latest posts
@rl_dane Then this is more mysterious. #FreeBSD ports does not patch out #wordexp in the config processing from x11-wm/sway like #OpenBSD ports does, and command substitution via backticks in the Almquist shell wordexp builtin itself works.
#Illumos has another #wordexp implementation (originating with Mortice-Kern, no less!) that expects a Korn (93) shell and uses its printf (and set -o), which might be tweakable to function with #OpenBSD's PD Korn shell; but like the GNU C l
Could #OpenBSD easily be improved to provide the standard #wordexp? It's a tricky one. The FreeBSD and NetBSD implementations rely on sh being the Almquist shell with an undocumented wordexp builtin, but sh is a Korn shell variant on OpenBS
#wordexp across platforms
every network with a public tag surfaceFollow #wordexp straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/wordexp