#jwt
Live, measured metrics for the hashtag #jwt from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jwt
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 05:18 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 05:18 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:18 UTCEverything below is measured over the latest 40 public posts (spanning ~3301 hours).
Posting hours (UTC) — busiest: 18:00
Languages: English (19) · Russian (14) · German (2) · Japanese (2) · Chinese (Taiwan) (1) · Portuguese (1)
Avg boosts / post: 0.5
Top of the latest posts
Software engineer Mukesh Murugan writes this recent first in-depth article in a three-part series covering roles, claims, and policies for JWT-based authentication, and authorization in ASP.NET Core web apis using C#. His blog (https://code
🚨 WoB PATTERN: The 'Trust Me' JWT Parser One of my favorites, since we saw it in the wild... "Why pull in a heavy dependency like 'jjwt' or 'jose'? Parsing a JWT is just splitting a string by dots and decoding Base64. Easy!" The result of
Test JWT clock skew tolerance by manually shifting system time with timedatectl on Ubuntu 22.04, Debian 12, or RHEL 9. Validate tokens with known iat, nbf, exp timestamps against tolerance windows (e.g., 30s) and log discrepancies. #jwt #cl
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/jwt