#JWTS
Live, measured metrics for the hashtag #JWTS from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jwts
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-10-04 06:25 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-10-04 06:25 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-04 06:25 UTCEverything below is measured over the latest 2 public posts (spanning ~14115 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Top of the latest posts
Ah, the wisdom of 2026: #Stop #using #JWTs because... reasons. 🚫🔑 Just like switching tabs, maybe if you reload this article enough times, the #logic will magically appear. 🌪💥 https://gist.github.com/samsch/0d1f3d3b4745d778f78b230cf6061
https://auth0.com/blog/test-authorization-in-aspnet-core-webapi-with-user-jwts-tool/ - using #ASPnet dev #JWTs in #UnitTests. Awesome article https://www.linkedin.com/in/andreachiarelli/.
#jwts across platforms
every network with a public tag surfaceFollow #jwts 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/jwts