#edgedb
Live, measured metrics for the hashtag #edgedb from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #edgedb
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 · mastodon.social (Mastodon public tags API) · fetched 2026-07-28 09:55 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-07-28 09:55 UTCNo related tags with measured usage found for #edgedb.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-28 09:55 UTCEverything below is measured over the latest 17 public posts (spanning ~33404 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (12) · German (4)
Avg boosts / post: 0.4
Top of the latest posts
I went through the #FastAPI tutorial for #EdgeDB 3.0 and I gotta say it's come a long way since I tried it last. This is a very quick way to get from zero to a modern asynchronous type-annotated #Python app. And no ORM in sight! https://www
I absolutely love #EdgeDB, but they are flying through major versions. I feel like if 3.0 and 4.0 are only 4 months apart, maybe we still haven't reached 1.0.
The downside: #EdgeQL is currently (seemingly) only implemented by #EdgeDB. EdgeDB *is* a relational database at heart (they don't get tired of mentioning #Postgres) and EdgeQL queries *do* compile to SQL (from what I can tell, this is not
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/edgedb