#uvbuild
Live, measured metrics for the hashtag #uvbuild from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #uvbuild
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 05:09 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 05:09 UTCNo related tags with measured usage found for #uvbuild.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 05:09 UTCEverything below is measured over the latest 4 public posts (spanning ~527 hours).
Posting hours (UTC)
Languages: Polish (2) · English (2)
Avg boosts / post: 3.3
Used together with
Top of the latest posts
Let's compare #PEP517 backends for pure #Python packages: #flit-core: 51 KiB sdist, no dependencies, 0.05 s to install, ~150 KiB after installing, works everywhere #UvBuild: 300 KiB sdist, requires ~250 crates (54 MiB download, ~600 MiB .ca
Porównajmy backendy #PEP517 dla paczek napisanych w samym Pythonie: #flit-core: 51 KiB archiwum źródłowe, bez zależności, instaluje się 0,05 s, ~150 KiB po zainstalowaniu, działa wszedzie #UvBuild: 300 KiB archiwum, wymaga ~250 zależności c
Jakby ktoś nie śledził, to informuję, że #UvBuild jednak powstaje — i to straszna wiadomość dla wszystkich tych, których system nie jest wspierany przez #RustLang. O co chodzi? Otóż, uv-build to system budowania #PEP517 dla projektów w "czy
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/uvbuild