#neatvi
Live, measured metrics for the hashtag #neatvi from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #neatvi
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-11-05 09:21 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-11-05 09:21 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-11-05 09:21 UTCEverything below is measured over the latest 4 public posts (spanning ~1655 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 1.8
Top of the latest posts
Kernel upgraded to Linux 6.19.6 on Slackware. System stable so far... Rachael Tyrell from Blade Runner keeping an eye on things. #slackware #kernel #dwm #st #slackfetch #nvi #neatvi
Just measured memory usage of nvi vs neatvi opening a ~500KB file (/usr/include/*.h concatenated): nvi 5184 KB neatvi 1960 KB 2.6x less RSS neatvi wins without syntax highlighting even in the picture. The difference is likely nvi's Berkeley
I decided to make that list anyway. http://jdebp.info/FGA/vi-family.html #vi #VIM #NeoVIM #viless #neatvi #nextvi #nvi #elvis #STEVIE
#neatvi across platforms
every network with a public tag surfaceFollow #neatvi straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/neatvi