#usernamespace
Live, measured metrics for the hashtag #usernamespace from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #usernamespace
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 07:10 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 07:10 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:10 UTCEverything below is measured over the latest 3 public posts (spanning ~627 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 1.3
Top of the latest posts
💥🔧 Ubuntu's #unprivileged user namespace restrictions are about as useful as a chocolate teapot, as revealed by three new bypasses. Meanwhile, #security advisories pile up like unread emails, and #Ubuntu users everywhere double down on th
OSS-SEC: Three bypasses of Ubuntu's unprivileged user namespace restrictions https://seclists.org/oss-sec/2025/q1/253 #HackerNews #OSSSEC #Ubuntu #Security #Vulnerabilities #UserNamespace #Bypasses #OpenSource
#TIL: #Firefox on #Linux works fine with user.max_user_namespaces = 0 as well as with user.max_user_namespaces = 100 but not with user.max_user_namespaces = 1 which seems to have been set by default on my #DebianUnstable since last week or
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/usernamespace