#tlsv13
Live, measured metrics for the hashtag #tlsv13 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tlsv13
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 20:02 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 20:02 UTCNo related tags with measured usage found for #tlsv13.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 20:02 UTCEverything below is measured over the latest 4 public posts (spanning ~57794 hours).
Posting hours (UTC)
Languages: English (2) · German (1)
Avg boosts / post: 1.5
Top of the latest posts
relayd(8) and httpd(8) TLS settings update. https://www.undeadly.org/cgi?action=article;sid=20260629165750 #openbsd #relayd #httpd #tls #ssl #tlsv13 #tlsv12 #security #cryptography #crypto
RIOT Summit 2018 @ Amsterdam - TLS v1.3 and RIOT OS https://makertube.net/w/oc3Zdb3e28eFZCfgS6sfwA
Ah guck, und ne Erklärung worans lag kam auch gleich noch hinterher. > In fact this problem is caused by Google because in the updated SSL provider TLSv1.3 is disabled by default. I think this is insane, but who am !? Muss ihm da völlig zus
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/tlsv13