#ngi0discovery
Live, measured metrics for the hashtag #ngi0discovery from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ngi0discovery
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-10-03 03:05 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-10-03 03:05 UTCNo related tags with measured usage found for #ngi0discovery.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-03 03:05 UTCEverything below is measured over the latest 2 public posts (spanning ~12671 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0.5
Used together with
Top of the latest posts
Had an interesting conversation with someone from the IETF about #multicast today. Some folks have been trying to solve the problem of getting multicast streams from unicast only sources (Off-net Sourcing) such as browsers. This happens to
Sid Meier, eat your heart out 😃 https://librecast.net/2019-08-078.html That's just the #NGI0Discovery bits up to October 2022. Well, most of it. Damn the interconnectedness of all things.
#ngi0discovery across platforms
every network with a public tag surfaceFollow #ngi0discovery 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/ngi0discovery