#nvimdap
Live, measured metrics for the hashtag #nvimdap from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #nvimdap
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 05:18 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 05:18 UTCNo related tags with measured usage found for #nvimdap.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:18 UTCEverything below is measured over the latest 9 public posts (spanning ~11893 hours).
Posting hours (UTC)
Languages: English (9)
Avg boosts / post: 0.9
Top of the latest posts
Another great video from TJ: https://www.youtube.com/watch?v=lyNfnI-B640 I just wish, it was released a few days ago 😅 #NeoVIM #nvimdap
I managed to configure #ddev , #neovim #nvimdap , and #xdebug to work together, but it's definitely more tricky than debugging in #vscode . So far, the first thing I've found easier to do in vscode than in neovim.
The debug adapter protocol was extended a while ago to let debug adapters provide the source location for variables and evaluate responses. There's now a PR up that adds a tagfunc to nvim-dap to use that info if available. That lets users j
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/nvimdap