#shockingevent
Live, measured metrics for the hashtag #shockingevent from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #shockingevent
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 12:25 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 12:25 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:25 UTCEverything below is measured over the latest 2 public posts (spanning ~3355 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Top of the latest posts
In a shocking turn of events, apparently the entire #internet is held together by #JavaScript and a #cookie 🍪⁉️ Without these sacred relics, the digital realm refuses to let you proceed—because who needs web content when you can have infin
🎉 BREAKING NEWS: A shocking development—an 86-year-old man succumbs to being hit by high-velocity Israeli air! ☠️ #NPR, in their infinite wisdom, crams this into their labyrinth of menus and buzzwords, all while trying to sell you tote bag
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/shockingevent