#tls1
Live, measured metrics for the hashtag #tls1 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tls1
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 23:31 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 23:31 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 23:31 UTCEverything below is measured over the latest 14 public posts (spanning ~61307 hours).
Posting hours (UTC) — busiest: 06:00
Languages: English (13) · French (1)
Avg boosts / post: 0.4
Top of the latest posts
“Post-quantum Cryptography (#PQC) isn’t a buzzword. It’s a practical response to a looming issue…” Learn how to future-proof your #webserver with #TLS1.3, #PQC, certs, & compliance in this article by Linux Professional Institute (LPI) Board
I just noticed I was running not only my Nextcloud, but also my Matrix and Fediverse (this one) servers with #TLS1.3 only by accident 😮 I thought that would lead to massive compatibility issues. And maybe this setting is related to some is
https://internet.nl/site/www.flickr.com/2292060/ some enhancements #nodnssec #nohsts ,stop #tls1.0 #tls1
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/tls1