#lspmode
Live, measured metrics for the hashtag #lspmode from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #lspmode
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 12:42 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 12:42 UTCNo related tags with measured usage found for #lspmode.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:42 UTCEverything below is measured over the latest 10 public posts (spanning ~32676 hours).
Posting hours (UTC)
Languages: English (10)
Avg boosts / post: 0.4
Top of the latest posts
I’ve had a keybinding for `consult-lsp-diagnostics` from https://github.com/gagbo/consult-lsp/ (blending #consult & #lspmode in #Emacs) for years but I only just started using it. It’s so convenient. With vertico, I can even preview results
Spent the morning replacing lsp-mode with Eglot due to slop code in the former. Seems to have gone smoothly, I'm really enjoying the snappiness of it, using lsp-mode by comparison is like wading through molasses. Am using the following: * j
Seems like lsp-mode is accepting slop contributions. Time to jump ship to eglot. #emacs #lspmode
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/lspmode