#pgconfde
Live, measured metrics for the hashtag #pgconfde from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pgconfde
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:30 UTC1 uses by 1 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:30 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:30 UTCEverything below is measured over the latest 40 public posts (spanning ~2261 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (36) · German (4)
Avg boosts / post: 1.4
Top of the latest posts
Radim Marek from boringSQL talks about tests for SQL - It works on my database - Regression testing of SQL queries #postgresql #pgconfde #boringsql
We're ready for 2026.pgconf.de #postgresql #pgconfde
Bruce Momjian from EDB is explaining What's Missing in Postgres? #postgresql #edb #pgconfde #brucemomjian
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/pgconfde