#libalpm
Live, measured metrics for the hashtag #libalpm from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #libalpm
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-31 06:53 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-31 06:53 UTCNo related tags with measured usage found for #libalpm.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-31 06:53 UTCEverything below is measured over the latest 2 public posts (spanning ~7211 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 1.5
Top of the latest posts
Ok, small announcement. With latest version of #Pacman (6.1) the #AUR helpers like #Yay and #Paru break so does #Pamac. They require latest #libalpm patches... Wait for updates... #FOSS #Linux #OpenSource
Implementing #libalpm / #pacman compatible vercmp() in #rustlang tends to get a bit bizarre: "" < "1" but "" > "a" and "1.a001a.1" == "1.a1a.1" (this is all essentially #rpm behavior btw!) https://gitlab.archlinux.org/archlinux/alpm/alpm-ty
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/libalpm