#TorBrowserBug
Live, measured metrics for the hashtag #TorBrowserBug from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #torbrowserbug
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 09:07 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 09:07 UTCNo related tags with measured usage found for #torbrowserbug.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:07 UTCEverything below is measured over the latest 3 public posts (spanning ~27185 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 1
Used together with
Top of the latest posts
Hi @torproject can you see this toot? if so, pls tell me, while working on something i appear to have found a problem with tor browser (possibly firefox! but i don't use ff), thanks. #torbrowser #firefox #torbrowserbug
We found a fairly glaring bug in #Firefox that affects Tor. That we thought was actively fixed years ago. Cannot discuss further. Any genuine #Firefox or #TorBrowser devs on fedi? #FirefoxBug #TorBrowserBug #Mozilla
@adnan360 The difference in font size is huge. Entire fontsize is approx. 50% larger by adding 'courier' before 'monospace'. It's either a #FirefoxBug or a #TorBrowserBug in our honest opinion. Don't get me wrong though it looks nice at the
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/torbrowserbug