#aisec
Live, measured metrics for the hashtag #aisec from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #aisec
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 04:51 UTC2 uses by 2 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 04:51 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 04:51 UTCEverything below is measured over the latest 24 public posts (spanning ~32047 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (21) · French (2) · German (1)
Avg boosts / post: 0.8
Top of the latest posts
🧠 AI + Security Automation — What do you want first? Which agent should I open-source next? 🔘 Prompt injection defender 🔘 CVE → exploit correlator 🔘 Smart contract auditor 🔘 Recon bot for OSINT / endpoints Vote, @mention, or drop your
RE: https://infosec.exchange/@Hacktivate/115581917628259124 ⚡ 3 Fast Checks Every Network Should Run Today 1️⃣ Unknown devices on VLANs? 2️⃣ Unused open ports pre-attack? 3️⃣ Default creds still active anywhere? You don’t need a full audit
You know I hadn't thought of the impact of a language barrier for guardrails. https://www.darkreading.com/cybersecurity-operations/europes-multilingual-reality-exposes-ai-security-gaps #aisec #guardrails
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/aisec