#jsdb5
Live, measured metrics for the hashtag #jsdb5 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jsdb5
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-28 09:13 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-28 09:13 UTCNo related tags with measured usage found for #jsdb5.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 09:13 UTCEverything below is measured over the latest 3 public posts (spanning ~24 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 1
Top of the latest posts
JSDB 5.1.0 published¹ 🎉 • Forgetting to pass a custom class that’s persisted in your database in your `JSDB.open()` call now throws instead of corrupting your database by falling back to using an untyped object. • Added JSDF ver. 2 to 3 da
JSDB 5.0.1 published 🎉 • Fixes #14: Crash if DataProxy getHandler() called on object with null prototype. (https://codeberg.org/small-tech/jsdb/issues/14) To install update: npm install @small-tech/[email protected] Learn more about JSDB: https:/
To really drive home the above 👆 point that 100% test coverage does not mean ‘bug free’, just found a bug in JSDB¹ 5.0.0 where running JSON.stringify() on a complex custom object (actually: the automatic Proxy of the custom object created
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/jsdb5