#privesc
Live, measured metrics for the hashtag #privesc from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #privesc
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 04:21 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 04:21 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 04:21 UTCEverything below is measured over the latest 36 public posts (spanning ~71113 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (28) · German (2) · French (1) · Polish (1) · Dutch (1) · Swedish (1)
Avg boosts / post: 2.3
Top of the latest posts
What do you use on FreeBSD for privilege escallation? I recently tried out mdo (mac_do) and like it quite but. Included in the base system, flexible rules (although not super intiitive) and not as limtied as good old "su" ... #freebsd #priv
Just published a proof-of-concept exploit for CVE-2025-32463, a new Linux privilege escalation vulnerability affecting sudo discovered and disclosed by Stratascale about 2 weeks ago. The PoC is available on GitHub. A full technical writeup
Recent privilege escalation vulnerabilities in GNU C Library #glibc widely used in many #Linux distributions such as #Debian, #Ubuntu, #Fedora and others. CVE-2023-6246 #privesc #vuln can be triggered via #syslog by using long program name
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/privesc