#browserbug
Live, measured metrics for the hashtag #browserbug from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #browserbug
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 11:55 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-07-27 11:55 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:55 UTCEverything below is measured over the latest 4 public posts (spanning ~12118 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 6
Top of the latest posts
My cross-platform and cross-browser NTLM bug is public: https://issues.chromium.org/issues/40080133 Kudos to @Bitquark who reported it separately. Kudos also to @torproject and @mozilla who did make efforts. #security, #wontfix, #threatinte
I just found the weirdest bug in Safari @webkit When swapping the class name of two DOM nodes, it tells JavaScript that attribute changed, but the "real" DOM and painted screen don't change, permanently out of sync. https://treasure21.timot
Chromium not always rendering updates to SVG sprites? What are these shenanigans. #chromium #gecko #svg #sprites #browserBug
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/browserbug