#gram
Live, measured metrics for the hashtag #gram from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #gram
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 20:37 UTC2 uses by 2 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 20:37 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 20:37 UTCEverything below is measured over the latest 40 public posts (spanning ~3379 hours).
Posting hours (UTC) — busiest: 06:00
Languages: English (34) · Indonesian (3) · Czech (2) · Swedish (1)
Avg boosts / post: 0.9
Top of the latest posts
Thanks to a work-in-progress Homebrew cask by Andi Péter (https://codeberg.org/GramEditor/gram/issues/15#issuecomment-11159294), I was just able to quickly install and play with the new Gram code editor (https://codeberg.org/GramEditor/gram
For many years I used #vim as my editor. I still use it a lot, but in recent years I have been using VSCode as my code editor. I recently read a blog by John Arundel on his dev setup and he mentioned he uses #zed. I started to experiment wi
After moving from #Zed to #Gram as my main code editor, my muscle memory still has to adjust to the different CLI name. Configuring an alias feels counterproductive though. #ZedEditor #GramEditor
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/gram