#vendorsecurity
Live, measured metrics for the hashtag #vendorsecurity from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #vendorsecurity
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 05:07 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 05:07 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 05:07 UTCEverything below is measured over the latest 5 public posts (spanning ~10070 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0.8
Top of the latest posts
Third-party breach, 38M impacted, European e-commerce sector. ManoMano disclosed unauthorized access linked to a subcontracted customer support provider. Exposed data reportedly includes PII and support communications. Authorities notified:
OpenAI has reported that a breach at Mixpanel exposed limited API-user metadata, including names, emails, coarse location, OS/browser details and IDs. This was not an OpenAI breach, and no chat content, credentials, API keys or payment data
OpenAI confirmed that limited API-user data was exposed through a breach at its previous analytics provider, Mixpanel. The dataset included names, emails, coarse location, user/organization IDs, and technical metadata — but no chats, passwo
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/vendorsecurity