#stun
Live, measured metrics for the hashtag #stun from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #stun
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 02:39 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-29 02:39 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 02:39 UTCEverything below is measured over the latest 38 public posts (spanning ~64947 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (20) · German (9) · Russian (4) · French (4)
Avg boosts / post: 1
Top of the latest posts
Few days ago I successfully configured #coturn to have a TURN/STUN server for in-family calls. But … looks like bots or some bad guys constantly trying to connect to my TURN server to use it for something :-( Of course, it is impossible, si
To all #jitsi admins out there: if you don't want to use the #STUN servers of Google due to #privacy concerns, you can use mine at stun:kopanyo.com:3478. It's only STUN, no TURN. I don't keep any logs... and I am not interested in any data
An XMPP developer pointed me to configuration issues with the trashserver.net TURN/STUN service. This service is required for video call setups and is probably not used by a lot of people, but still: It was broken and might have caused some
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/stun