#rtic
Live, measured metrics for the hashtag #rtic from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #rtic
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 10:02 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 10:02 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 10:02 UTCEverything below is measured over the latest 8 public posts (spanning ~21376 hours).
Posting hours (UTC)
Languages: English (6) · German (1) · Russian (1)
Avg boosts / post: 0.4
Top of the latest posts
Da ich mich gerade ein wenig mit Digitaler Signalverarbeitung beschäftige, suche ich ein #RTOS, mit dem ich harte Realtime Tasks laufen lassen kann. Dabei bin ich über #RTIC gestolpert und habe es gerade mal auf einem STM32H7A3 zum Laufen g
So I think I got my head around async/await in #Rust, and I also know how IRQs work on embedded systems. But it was oddly hard to find a good article on exactly how to join up those two bits of knowledge: how to ".await" where what you're w
despite all the hate speech towards #rustlang i'm working on a small and cool patch set and tooling for #rust #linux tree ;-) doing it on side but i have pretty solid idea what i want. and also is in reach of what i generally have done in k
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/rtic