#astronvim
Live, measured metrics for the hashtag #astronvim from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #astronvim
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:36 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 20:36 UTCNo related tags with measured usage found for #astronvim.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 20:36 UTCEverything below is measured over the latest 34 public posts (spanning ~28704 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (28) · Spanish (1) · Swedish (1)
Avg boosts / post: 0.4
Top of the latest posts
Its been one week since I’ve been trying #Helix I can say that I’ve actually been a bit more efficient with helix than I have been with #NeoVim (dont hurt me) I understand that using #VI motions is a great move since you dont have to go aga
I like my #riscV #MilkV Jupiter board, but it's far from ready for daily #programming business. Standard tools are missing or not working: #VSCodium cannot be compiled, because #NodeJS dependencies have no RISC-V support. #neovim cannot be
@thedoctor @dpom I found it easier to take a neovim distribution (#LazyVim in my case, but I plan to test #AstroNvim ) and change that to suit my taste.
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/astronvim