#bitemporal
Live, measured metrics for the hashtag #bitemporal from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #bitemporal
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 04:56 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 04:56 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-11-09 04:56 UTCEverything below is measured over the latest 7 public posts (spanning ~26610 hours).
Posting hours (UTC)
Languages: English (7)
Avg boosts / post: 0.9
Top of the latest posts
⏱️ Poor man's bitemporal data system in SQLite and Clojure https://www.evalapply.org/posts/poor-mans-time-oriented-data-system/index.html #database #software #time #bitemporal #clojure #sqlite #analytics
Very excited about XTDB 2.0 early access https://github.com/xtdb/xtdb/tree/2.x and its SQL support -- so I wrote an experimental extension to next.jdbc to support XTDB! https://github.com/seancorfield/next.jdbc.xt #clojure #bitemporal
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
What “bitemporal” means
WikipediaA temporal database stores data relating to time instances. It offers temporal data types and stores information relating to past, present and future time. Temporal databases can be uni-temporal, bi-temporal or tri-temporal.
“Temporal database” on Wikipedia (CC BY-SA) →#bitemporal across platforms
every network with a public tag surfaceFollow #bitemporal 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/bitemporal