#infovis
Live, measured metrics for the hashtag #infovis from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #infovis
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-29 19:08 UTC1 uses by 1 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-29 19:08 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 19:08 UTCEverything below is measured over the latest 40 public posts (spanning ~114865 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (38) · Japanese (1) · German (1)
Avg boosts / post: 2.5
Top of the latest posts
Just realized I never posted an #introduction, so here we go: Hi 👋 my name is Hagen and currently I'm pursuing my PhD in computer science. My research interests include Information Visualization, Scientific Visualization techniques, and Co
We are exploring some ambitious ideas around reducing external dependencies and relying more on our own libraries across MISP and related tooling. Over the past year, we have been working on a replacement network graph library for the new M
A map of Redfern if you scaled the roads by roughly how long you spend waiting at traffic lights (if you walked at 1.2m/s instead) (Better Intersections data) info vis/cartography experts: any ideas how I could automate this? I'm thinking s
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/infovis