#sqlcodelenses
Live, measured metrics for the hashtag #sqlcodelenses from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #sqlcodelenses
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 22:23 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 22:23 UTCNo related tags with measured usage found for #sqlcodelenses.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 22:23 UTCEverything below is measured over the latest 2 public posts (spanning ~427 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0.5
Top of the latest posts
Our new #MarkdownSQL #ProDataTools 🛠️ now support SQL code fences in #Quarto docs, and add #SQLCodeLenses 🧐 & #SQLBookmarks 📑 to .qmd markdown documents in #VSCode IDE. Quick demo of setting up local HR #SQLite database with #SQLTools VS
There are over 538K SQL code blocks in docs on GitHub: 🔎 https://github.com/search?q=%2F%60%60%60sql%5B%5Cs%5CS%5D*%3F%60%60%60%2F+language%3AMarkdown&type=code We believe SQL code in docs should be runnable. We created #SQLCodeLenses with
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/sqlcodelenses