#upstreams
Live, measured metrics for the hashtag #upstreams from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #upstreams
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-09-26 23:46 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-09-26 23:46 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-09-26 23:46 UTCEverything below is measured over the latest 2 public posts (spanning ~7791 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 1
Top of the latest posts
I'm going to stop re-tooting about the #xz #backdoor as I'm pretty sure everyone is aware now. I'm sure there will be further analysis and recommendations in the following days and hopefully concrete action other #upstreams can take to tigh
Some #corporate #opensource #python #upstreams are more cursed than others. We experience packager drain on #molecule and #ansible related packages, as upstream knowingly breaks compatibility from time to time and doesn't guard or test agai
#upstreams across platforms
every network with a public tag surfaceFollow #upstreams 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/upstreams