#browserinthebrowser
Live, measured metrics for the hashtag #browserinthebrowser from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #browserinthebrowser
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 · mastodon.social (Mastodon public tags API) · fetched 2026-11-15 15: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 · mastodon.social (Mastodon public search API) · fetched 2026-11-15 15:58 UTCNo related tags with measured usage found for #browserinthebrowser.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-11-15 15:58 UTCEverything below is measured over the latest 10 public posts (spanning ~14060 hours).
Posting hours (UTC)
Languages: English (7) · German (1) · Greek (1) · Polish (1)
Avg boosts / post: 0.1
Top of the latest posts
Cyberprzestępcy kradną konta Steam graczy CS2 za pomocą techniki Browser-in-the-Browser (BitB) Kilka dni temu zespół Silent Push poinformował o namierzeniu kampanii phishingowej targetującej graczy Counter-Strike 2 na Steam z wykorzystaniem
Fake recruiters, real MFA bypass: a BitB popup relays Google codes live to steal work sessions. 9 detections, 19 IOCs. Full analysis + IOCs: https://intel.threadlinqs.com/threat/TL-2026-4994?utm_source=mastodon #ThreatIntel #BrowserintheBro
RE: https://social.tchncs.de/@Netzpalaver/117473386094314001 Eine aktuelle Phishing-Kampagne ködert Nutzer mit angeblich kostenlosen Abonnements für die KI „Claude-Max“, um an deren Google-Zugangsdaten zu gelangen. Sicherheitsforscher von M
#browserinthebrowser across platforms
every network with a public tag surfaceFollow #browserinthebrowser 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/browserinthebrowser