#DexieJS
Live, measured metrics for the hashtag #DexieJS from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dexiejs
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-13 18:57 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-13 18:57 UTCNo related tags with measured usage found for #dexiejs.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-11-13 18:57 UTCEverything below is measured over the latest 2 public posts (spanning ~10317 hours).
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 0
Used together with
Top of the latest posts
Good morning. It looks like rain! Instead of giving you the digest of me reading the accumulated traffic from overnight. There was stuff like quote boosts displayed via browser extension. I'm going to say that I'm surprised about a few thin
I get that there might be some complexity involved with flushing data, but after using IndexDB in production I don’t understand why it isn’t more popular. Doing complex queries, storing large amounts of data, consolidation, it’s all so clea
#dexiejs across platforms
every network with a public tag surfaceFollow #dexiejs 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/dexiejs