#imsg
Live, measured metrics for the hashtag #imsg from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #imsg
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-11-11 09:19 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-11-11 09:19 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-11-11 09:19 UTCEverything below is measured over the latest 2 public posts (spanning ~16123 hours).
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 0
Used together with
Top of the latest posts
Where is /usr/include ? O_o https://codeberg.org/OpenBSD/src/src/branch/master I want to point to /usr/include/imsg.h because it is modern (i think) and it has an example of a struct with a function pointer in it. I have been looking for ex
@claudiom -- thanks for the recent fixes to #imsg for non-BSD systems. I can confirm this working in both #tmux and #got One thing I'm interested in knowing is what prompted these API changes to imsg? Not that I think they're wrong, but som
#imsg across platforms
every network with a public tag surfaceFollow #imsg 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/imsg