#publicBSOD
Live, measured metrics for the hashtag #publicBSOD from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #publicbsod
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-29 20:58 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-29 20:58 UTCNo related tags with measured usage found for #publicbsod.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 20:58 UTCEverything below is measured over the latest 2 public posts (spanning ~24640 hours).
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 0.5
Top of the latest posts
July 12, 2026. On rail between Kajaani and Oulu, Finland. Nikon D780, AF-S Nikkor 50mm f/1.8G. Sometimes when the Finnish InterCity trains go through unfathomable stretches of wilderness they become . Haxx0r'd! PhUtUr3 Iz N0w! #photo #finla
#publicBSOD why do they even run windows? Licensing costs, complexity, and the fragility of Windows all suggest this is a terrible idea.
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/publicbsod