#devenv
Live, measured metrics for the hashtag #devenv from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #devenv
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 · mas.to (Mastodon public tags API) · fetched 2026-07-27 13:10 UTC1 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-27 13:10 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-27 13:10 UTCEverything below is measured over the latest 40 public posts (spanning ~12594 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (36) · German (3)
Avg boosts / post: 5.7
Top of the latest posts
If you're using #devenv for your projects, please note that the new `generate` command in 1.4.0 uses your repository content. It tars up all files it can find through `git ls-files -z`³ and exfiltrates them to the service. It handles `DO_NO
Not really surprising though I guess, its the corporate way of doing things. You do something shady, get called out, apologize in an hand wavy, noncommittal kind of way, promise to do better, and then instead of doing anything wait until it
So, I gave #devenv a try. I'm used to work with #nix #flakes but I have to admin the devenv.nix file is less cluttered which lead to a better UX. But this comes at the cost of an extra devenv.yaml file. Why not, not a fan, but it works. But
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/devenv