#nixpkg

Live, measured metrics for the hashtag #nixpkg from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #nixpkg

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.

$520.70/ year · 6-character #name
Claim #nixpkg$520.70/yrBuy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
11
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 11
0.4
Avg reactions / post
Mastodon · last 11

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 17:59 UTC
0
07-22
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27
0
07-28

0 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 17:59 UTC

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 17:59 UTC

Everything below is measured over the latest 11 public posts (spanning ~60987 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: English (11)

Avg boosts / post: 0.2

Top of the latest posts

  • Today's minor `nixpkgs` bug is the "excessive" runtime closure size of `meld` package: https://github.com/NixOS/nixpkgs/pull/265454 There `meld` retained development-style dependencies like headers for `libffi` which `meld` should not use (

    Sergei Trofimovich@trofi312023-11-04 16:00 UTCView post →
  • Today's trivial `nixpkgs` bug is https://github.com/NixOS/nixpkgs/pull/270013#issuecomment-1826668194. There `sway` attribute type was turned from a derivation into a lambda function. That broke cases where `sway` was augmented with an `.ov

    Sergei Trofimovich@trofi102023-11-26 07:07 UTCView post →
  • googling for how to update the checksum in a #nixpkg is surprisingly difficult. You get more incorrect solutions than search results. Why can't you just use a normal sha256 of the exact file downloaded from the url that is literally right a

    Klaus Frank@[email protected]002025-08-31 12:20 UTCView post →

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/nixpkg