#TrojanSource
Live, measured metrics for the hashtag #TrojanSource from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #trojansource
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-07-27 13:35 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 13:35 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-27 13:35 UTCEverything below is measured over the latest 4 public posts (spanning ~24455 hours).
Posting hours (UTC)
Languages: German (2) · English (2)
Avg boosts / post: 0
Top of the latest posts
Everything that's wrong with information technology these days in one single file: https://github.com/seanmiddleditch/gha-setup-ninja/blob/master/dist/index.js Any idea what this 1.1 MiB JavaScript is doing? It's the "compiled" version of t
i just got the answer from #github re: my #bugreport for their #TrojanSource #vulnerability : i found that the mitigation they put into place to protect against #TrojanSourceAttack until at least 4 weeks ago has been taken out again not by
#TrojanSource: Invisible Vulnerabilities https://www.lightbluetouchpaper.org/2021/11/01/trojan-source-invisible-vulnerabilities/ Clever. #TrojanSourceAttack #Unicode
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/trojansource