#sndio
Live, measured metrics for the hashtag #sndio from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #sndio
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 14:33 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-27 14:33 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 14:33 UTCEverything below is measured over the latest 40 public posts (spanning ~57294 hours).
Posting hours (UTC) — busiest: 02:00
Languages: English (31)
Avg boosts / post: 1
Top of the latest posts
currently looking at #sndio to try and implement audio devices for #uxn playing audio shouldn't block, but not sure what the easiest way to then call the audio vector when the tone ends is
@sourcerer @vermaden speaking of audio, the mess (really) started when #Linux devs deemed their #OSS variant "unfixable" and started with #ALSA. Introducing a shared lib here (libasound) lead to tighter coupling. And it got worse adding com
@RL_Dane @taur10 #Pulseaudio has #sndio support as well. Sadly it's not compiled in on #ubuntu.
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/sndio