#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 · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 20:36 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 20:36 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 20:36 UTCEverything below is measured over the latest 7 public posts (spanning ~26610 hours).
Posting hours (UTC)
Languages: English (7)
Avg boosts / post: 1
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
Decisions decisions, which do I read first? #sql #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
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