#exec
Live, measured metrics for the hashtag #exec from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #exec
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-28 02:22 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-28 02:22 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 02:22 UTCEverything below is measured over the latest 33 public posts (spanning ~65868 hours).
Posting hours (UTC) — busiest: 19:00
Languages: English (25) · Russian (4) · Chinese (1) · French (1) · Italian (1) · Polish (1)
Avg boosts / post: 0.7
Top of the latest posts
You can debug programs with this TUI! 🔥 🕵️♂️ traceexec: Trace execve{,at} and pre-exec behavior. 🚀 Now supports GDB launcher: https://github.com/kxxt/tracexec/blob/main/demonstration/gdb-launcher/README.md 🦀 Written in Rust & built wit
Honest question: What are use-cases for performing exec while multi-threaded? Seriously, if I were to add a patch that prevents calling exec while multi-threaded in the kernel what possible use-case would break? #linux #kernel #exec
Oh, so you're tired of #the trusty fork() and exec() combo, huh? 😴 Well, let's reinvent the #wheel and complicate what's been working for decades. 🙄 Bravo, #LWN, for shedding light on the truly #groundbreaking idea of doing the same thing
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/exec