#nixshell
Live, measured metrics for the hashtag #nixshell from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #nixshell
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-27 10:24 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-27 10:24 UTCNo related tags with measured usage found for #nixshell.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 10:24 UTCEverything below is measured over the latest 26 public posts (spanning ~68683 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (24) · French (1) · German (1)
Avg boosts / post: 0.4
Top of the latest posts
Once you have experienced it you start to value the ephemeral nature of :nixos: #NixOS #nixshell's. Quickly need that one program but don't want it to clutter your system permanently? nix-shell -p git-extras This drops you into a shell with
Once again, defeated by `libiconv` 😭 Can someone explain to me what's the minimal set-up to get Cargo to pick it up in a #nixShell running on macOS? Edit: Never mind, once again I was defeated by my own bullshit 😅
Deploying a :nixos: #nixshell it is kind of funny that building gcc requires g++ ...
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/nixshell