#mdns
Live, measured metrics for the hashtag #mdns from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #mdns
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 13:39 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 13:39 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 13:39 UTCEverything below is measured over the latest 40 public posts (spanning ~51123 hours).
Posting hours (UTC) — busiest: 17:00
Languages: English (21) · French (8) · German (6) · Russian (4) · Spanish (1)
Avg boosts / post: 0.3
Top of the latest posts
@amadeus @loveyoumore We at OpenPrinting are aware of the problem and the bug is actually in CUPS and not in GNOME/GTK. See https://github.com/OpenPrinting/cups/issues/176 I have originally reported this one. See the answers of CUPS author
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
And in other other news, I thought I was going to have to spend this weekend #debuggering #mdns and #networking to try to see why one of my #Linux VMs (and only one of them) was being so stupidly slow and unstable after I got a new DSL mode
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/mdns