#rustasync
Live, measured metrics for the hashtag #rustasync from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #rustasync
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 00:57 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 00:57 UTCNo related tags with measured usage found for #rustasync.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 00:57 UTCEverything below is measured over the latest 10 public posts (spanning ~47367 hours).
Posting hours (UTC)
Languages: English (10)
Avg boosts / post: 3.1
Top of the latest posts
Yay! @notgull is working on `smol` integration with #axum! :awesome: https://github.com/notgull/smol-axum The smol #async runtime: https://github.com/smol-rs/smol #Tokio is not the end-all-be-all runtime. You should keep looking at alternat
@noboilerplate THIS! I think a lot of people inadvertently assume async #RustLang is so different from sync Rust, because the way it is - when in fact it's because of the (most popular) async runtime they're using. We should look way more i
*makes some happy screaming noise* :awesome: :ferris: #Rust will end this year with a long awaited feature that will define it's future: We will get "async fn and return-position impl Trait in trait" (#AFIT & #RPITIT). It will be stabilized
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/rustasync