#js8call
Live, measured metrics for the hashtag #js8call from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #js8call
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 11:23 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 11:23 UTCNo related tags with measured usage found for #js8call.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 11:23 UTCEverything below is measured over the latest 40 public posts (spanning ~15927 hours).
Posting hours (UTC) — busiest: 19:00
Languages: English (28) · Russian (7) · German (2) · French (2) · Catalan (1)
Avg boosts / post: 1.2
Top of the latest posts
It is very interesting to see #js8call being taken up by the CB crowd. The bright green stations are 27MHz - this is the last 15 minutes.
The next #JS8Call release 2.3.2 will have six different commits that were authored by me. Most prominently, my fix for the ALL.TXT receive timestamp bug. Many people in general and #hamRadio ops in particular are "hunters and gatherers". E.
#js8call Party today and #POTA 20m. Only 8 contacts. Thanks to them. No QSO on 15m. Anyway it was a good winter activation in #rennes Parc des Gayeulles. I think we are only few users operating #js8. It's sad.
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/js8call