#pulseaudio
Live, measured metrics for the hashtag #pulseaudio from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pulseaudio
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 · mastodon.social (Mastodon public tags API) · fetched 2026-07-27 08:45 UTC2 uses by 2 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-07-27 08:45 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 08:45 UTCEverything below is measured over the latest 40 public posts (spanning ~5468 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (32) · German (2) · Spanish (2) · Japanese (1) · Finnish (1) · Chinese (1)
Avg boosts / post: 0.6
Top of the latest posts
So, mein Manjaro-Arbeitssystem erfolgreich von #Pulseaudio auf #Pipewire umgestellt, weil #Niri sonst die Audiodevices nicht findet. Eigentlich ist Pipewire ja der Standard, aber die Installation ist wohl doch schon ne Weile her. Das Schöns
RealtimeKit has a new home next to @pipewire, and I just rolled out a new release ... give it a spin! https://gitlab.freedesktop.org/pipewire/rtkit #linux #linuxaudio #pipewire #pulseaudio
@screwlisp @AmenZwa @dougmerritt You can test the high frequency response of your microphone by smashing a fork and a tablespoon together. Or two forks. Or two tablespoons. I don't remember. The more annoying, eardrum-piercing the sound is,
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/pulseaudio