#informationdisclosure
Live, measured metrics for the hashtag #informationdisclosure from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #informationdisclosure
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 · mastodon.online (Mastodon public tags API) · fetched 2026-11-04 20:56 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-11-04 20:56 UTCNo related tags with measured usage found for #informationdisclosure.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-11-04 20:56 UTCEverything below is measured over the latest 28 public posts (spanning ~54213 hours).
Posting hours (UTC) — busiest: 07:00
Languages: English (27)
Avg boosts / post: 0.6
Top of the latest posts
Microsoft Issues Emergency Fix for Google Brotli Bug Microsoft has rushed out an emergency fix for a high-severity bug in Google's Brotli compression algorithm, warning that it could let hackers read or corrupt sensitive data. The update pa
Microsoft has released an emergency update for on-premises Exchange Server. The flaw could let an attacker who is already signed in read other users’ emails and attachments within the same organization; it did not grant access to other orga
IPMI Vulnerability Exposes 24,650 Server Management Interfaces A recent security researcher found that over 30% of server management interface passwords can be easily cracked using common wordlists and factory default patterns, exposing a m
#informationdisclosure across platforms
every network with a public tag surfaceFollow #informationdisclosure straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/informationdisclosure