#rtcqs
Live, measured metrics for the hashtag #rtcqs from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #rtcqs
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 22:47 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 22:47 UTCNo related tags with measured usage found for #rtcqs.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 22:47 UTCEverything below is measured over the latest 16 public posts (spanning ~10125 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (16)
Avg boosts / post: 0.7
Top of the latest posts
#LinuxAudio #BitwigStudio folk, I have installed and am attempting get the settings to be sticky for #rtcqs. The CPU Frequency Scaling set to performance and Simultaneous Multithreading set to disabled make the greatest positive difference
rtcqs v0.6.7 has just been released. This release fixes https://codeberg.org/rtcqs/rtcqs/issues/32 More info on the release: https://codeberg.org/rtcqs/rtcqs/releases/tag/v0.6.7 #rtcqs #LinuxAudio #RealTimeAudio #Linux #Python
Just released #rtcqs v0.6.6 with a fix for the SMT check. https://codeberg.org/rtcqs/rtcqs/releases/tag/v0.6.6 #LinuxAudio #LowLatencyAudio #RealTimeAudio #Linux
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/rtcqs