#prql
Live, measured metrics for the hashtag #prql from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #prql
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:12 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:12 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:12 UTCEverything below is measured over the latest 40 public posts (spanning ~26372 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (39) · Russian (1)
Avg boosts / post: 0.3
Top of the latest posts
A few obscure things that I wish end up winning over current dominant alternatives: - #SvelteJS over #ReactJS - #Podman over #Docker - #PRQL over #SQL - Berkeley's #Snap language over MIT's #Scratch - #ActivityPub over #Twitter - Geometric
I been slowly utilizing #prql instead of raw #sql. 😅 So far, it makes sense when doing analytical jobs. But for language support, it is far more natural to use DSL features made for languages like #ecto in #elixir. 😎 https://prql-lang.org
Playing with a reverse proxy and the #postgresql client/server protocol to automatically convert #prql queries to SQL (in #rustlang): https://jpmoresmau.blogspot.com/2023/06/prql-to-sql-transformation-on-fly.html
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/prql