#pavex
Live, measured metrics for the hashtag #pavex from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pavex
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-28 09:21 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-28 09:21 UTCNo related tags with measured usage found for #pavex.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 09:21 UTCEverything below is measured over the latest 28 public posts (spanning ~11042 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (27) · French (1)
Avg boosts / post: 1
Top of the latest posts
➡️ What you want: Reduce complexity for #RustLang backend development 🤔 ➡️ What you actually do: Let people write weird Rust code using macros generating more code in a crate that is fed to a custom transpiler that generates multiple Rust
Check out @algo_luca's talk at @Rustnationuk this March in London and dive into #backend development with #rustlang and #pavex! 🦀 ➡️ Grab your ticket: https://www.rustnationuk.com/
Six weeks have passed, it's time for another update on #pavex, the new #rust web framework I've been working on. I've focused on the router in March: trying to nail a good API and, most importantly, great error messages. It's looking quite
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/pavex