#consult
Live, measured metrics for the hashtag #consult from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #consult
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 09:13 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 09:13 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:13 UTCEverything below is measured over the latest 40 public posts (spanning ~50046 hours).
Posting hours (UTC) — busiest: 07:00
Languages: English (38) · Swedish (1) · Spanish (1)
Avg boosts / post: 1.1
Top of the latest posts
"The history of #Emacs completion frameworks is a progression from monolithic solutions toward composable ones." This is a comprehensive summary, with a thorough and fair history. A long read, but worth it. I plateaued at #Vertico #Orderles
I've recently added `consult-line` and `consult-focus-lines` to my #Emacs #Consult configuration and made `consult-line` the default search in lieu of `isearch-forward`. It seems to be working well, no apparent drawbacks so far. ``` (use-pa
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
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/consult