#krb5
Live, measured metrics for the hashtag #krb5 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #krb5
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 00:27 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 00:27 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 00:27 UTCEverything below is measured over the latest 11 public posts (spanning ~34807 hours).
Posting hours (UTC)
Languages: English (10) · Russian (1)
Avg boosts / post: 0.7
Top of the latest posts
I don't have to use the command line anymore to fetch #Kerberos tickets on my #librem5 as i made #krb5-auth-dialog adaptive (after some yak shaving):
@firstyear In the libkrimes README.md you write: "While RFC8009 does exist, it should be noted that no KDC we have tested with supports it in their latest versions (last tested June 2024)." I wonder which KDC you have tested, because AES-SH
Here we go. This is a Samba client and server implementing IAKerb support. The client uses the principal from the local KDC on the Samba server to get a Kerberos ticket using IAKerb. This means, we get a krbtgt and service ticket over the S
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/krb5