#SPIFFE
Live, measured metrics for the hashtag #SPIFFE from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #spiffe
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 13:33 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 13:33 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 13:33 UTCEverything below is measured over the latest 40 public posts (spanning ~27820 hours).
Posting hours (UTC) — busiest: 19:00
Languages: English (38) · Russian (1) · German (1)
Avg boosts / post: 0.4
Top of the latest posts
#Keycloak 26.4 is out with a lot of new capabilities for your self-hosted #iam: * #Passkeys * Client Authentication to use #SPIFFE or #Kubernetes service account tokens * Simplified deployments across multiple availability zones to boost av
🎉 Self-Hosted Human and Machine #Identity in #Keycloak 🎉 Our 26.4 release brings great updates with #passkeys and the latest security best practices for #OpenID Connect with #FAPI and DPoP. Automatically roll out and rotate client credent
You Have the Pieces. Now Build It 이 글은 AI 에이전트가 대규모로 배포되는 환경에서 비인간 워크로드의 신원 보증을 위한 통합 신원 아키텍처 부재 문제를 지적하며, 기존 표준 프로토콜(SPIFFE, OAuth 2.1 등)을 조합해 신뢰 기반 신원 체계를 구축할 것을 제안한다. 특히 SPIFFE를 기반으로 한 에이전트 신원 부여, 에이전트 게이트웨이에서의 정책 집행, 신뢰 브로커를 통한 자격 증명 보호
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/spiffe