#xtdb
Live, measured metrics for the hashtag #xtdb from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #xtdb
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 · mas.to (Mastodon public tags API) · fetched 2026-11-09 03:54 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-11-09 03:54 UTCNo related tags with measured usage found for #xtdb.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-11-09 03:54 UTCEverything below is measured over the latest 18 public posts (spanning ~39381 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (17) · Maltese (1)
Avg boosts / post: 0.3
Top of the latest posts
Anyone done work with #XTDB? It looks awesome to me, and the few hours I got to spend playing with it last night only made me more convinced. But obviously a huge difference between trying out a DB for fun and having to maintain one in prod
Has anyone done #bitemporal stuff with postgres 16? I understand SQL:2011 support has landed in postgres 18 but I'm hesitant about upgrading (being very conservative). I'm aware of https://github.com/scalegenius/pg_bitemporal and https://gi
```clojure (xt/execute-tx node [[:update '{:table :usage :bind [{:xt/id id} user] :unify [(from :usage [{:xt/id id} user-id]) (where (nil? user-id))] :set {:user-id user :guild-id "98393139101827072"}}]]) ``` I wanted to copy user->user-id
#xtdb across platforms
every network with a public tag surfaceFollow #xtdb straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/xtdb