#bugpocalpyse
Live, measured metrics for the hashtag #bugpocalpyse from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #bugpocalpyse
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 · mas.to (Mastodon public tags API) · fetched 2026-08-02 16:57 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-08-02 16:57 UTCNo related tags with measured usage found for #bugpocalpyse.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-08-02 16:57 UTCEverything below is measured over the latest 2 public posts (spanning ~125 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 2
Top of the latest posts
I've released VulnTrends v1.2.0. Rather than adding lots of new features, this update focuses on improving the foundations: • Higher quality data • Better analysis • New explanatory pages describing each metric and its limitations • Greater
Some people spend their holiday time on the beach. I play with websites, apparently. Don't tell Mrs P. I've enhanced the data gathered for my open source project VulnTrends (v1.1.0), and the picture is even more pronounced than the project
#bugpocalpyse across platforms
every network with a public tag surfaceFollow #bugpocalpyse 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/bugpocalpyse