#fga
Live, measured metrics for the hashtag #fga from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #fga
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 04:04 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 04:04 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 04:04 UTCEverything below is measured over the latest 26 public posts (spanning ~30075 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (23) · French (2) · Russian (1)
Avg boosts / post: 1.7
Top of the latest posts
Final post in the delegated access series. When a CIBA push expires before the approver responds, the answer isn't to fail the request - it's to separate the delivery ticket from the approval itself. Hybrid architecture, re-send mechanics,
Part three in the delegated access series. The approval flow: FGA resolves the approver, Auth0 CIBA sends a Guardian push, approval creates a delegation. Also: why CIBA consent does not persist across sessions, and why that's fine. https://
Second post in the series on delegated access — the implementation side. How Auth0, Auth0 FGA and an application data store fit together: the authorisation model, the delegation lifecycle, MFA step-up, and an on-behalf-of token where sub=pa
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/fga