#hackage
Live, measured metrics for the hashtag #hackage from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #hackage
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 07:52 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 07:52 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 07:52 UTCEverything below is measured over the latest 13 public posts (spanning ~48920 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (13)
Avg boosts / post: 0.9
Top of the latest posts
Guess who's an approved uploader on #hackage now?
Last week I submitted a new version of my currycarbon #haskell library to #hackage (see https://archaeo.social/@ClemensSchmid/111517617941502770). I made a mistake in the setup of my golden tests, which prevented the package from building o
We've fixed a bug (https://github.com/byorgey/MonadRandom/issues/53) in the MonadRandom package (https://hackage.haskell.org/package/MonadRandom) which could have *extremely rarely* caused it to crash when choosing from a weighted distribut
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/hackage