#NGI0Core
Live, measured metrics for the hashtag #NGI0Core from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ngi0core
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 05:25 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 05:25 UTCNo related tags with measured usage found for #ngi0core.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:25 UTCEverything below is measured over the latest 2 public posts (spanning ~3079 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 2
Top of the latest posts
Here is a new blog post 🗞️ containing a short overview of what happened around MPTCP over the past year! Still more work to do, but clearly a nice impact! https://blog.mptcp.dev/2025/01/27/one-year-NGI0-Core.html Thank you @nlnet and @NGIZ
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
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/ngi0core