#igmp
Live, measured metrics for the hashtag #igmp from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #igmp
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 08:03 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-27 08:03 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 08:03 UTCEverything below is measured over the latest 29 public posts (spanning ~48439 hours).
Posting hours (UTC) — busiest: 20:00
Languages: English (24) · German (3) · Russian (2)
Avg boosts / post: 0.4
Top of the latest posts
I'm a bit worried that the #IETF #GAAP draft (https://datatracker.ietf.org/doc/draft-ietf-pim-gaap/) again uses a single #multicast address for the control traffic. That already gives us headaches with #mDNS, which isn't easy to optimize wi
We also initially tried having #ClaudeCode implement the #IGMP / #MLD snooping, but it made several mistakes for one thing. And for another, of course doesn't know what was still broken on the chip. So from all that tinkering and digging in
Had found an issue with the #DSA #rtl83xx #IGMP / #MLD snooping code in #OpenWrt, it would always flood snoopable IP #multicast payload with no MDB entry, instead of dropping. Finally got some clue how this chip gets configured, it's a bit
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/igmp