#NixFlake
Live, measured metrics for the hashtag #NixFlake from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #nixflake
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 06:41 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 06:41 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 06:41 UTCEverything below is measured over the latest 16 public posts (spanning ~29264 hours).
Posting hours (UTC) — busiest: 21:00
Languages: English (16)
Avg boosts / post: 0.3
Top of the latest posts
Just a juicy bit for folks that happen to use #just and #nix and want them to play together... If your #nixflake outputs `devShells.default`, you can use a nix shell to run your Justfile tasks as script recipes, e.g.: ```justfile set script
I find it rather weird that defining your :nixos: #NixOS machine in your flake via `inputs.mynixpkgs.lib.nixosSystem` is *not* enough to have it actually use your `mynixpkgs`. No, you need to do this boilerplate stunt. Why doesn't it do it
Set up my first #nixflake for use with #direnv (used from #nushell) -- and once it all clicks its a thing of beauty.
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/nixflake