#authorisation
Live, measured metrics for the hashtag #authorisation from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #authorisation
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 05:34 UTC2 uses by 2 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 05:34 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 05:34 UTCEverything below is measured over the latest 14 public posts (spanning ~58762 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (13) · German (1)
Avg boosts / post: 0.4
Top of the latest posts
This is a very great OIDC overview. If are about to implement an application, you should consider using this for your user backend. If you are a user and want to know how "Sign-in with Google" or "Sign-in with Facebook" works, this is your
Kubernetes system is a vital part of many multi-tenant projects. As services that use it grow in scale and their policies become more complex, secure authorisation becomes a crucial issue. The new paper by Francesco Pizzato, Daniele Bringhe
Is there a standard for indicating that a given domain should use #OAuth for logins? For example, my webapp gets a signup or login attempt from [email protected] and does a lookup (maybe a #DNS TXT record?) and gets a result which tells
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/authorisation