#tls
Live, measured metrics for the hashtag #tls from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tls
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 06:24 UTC14 uses by 12 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 06:24 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 06:24 UTCEverything below is measured over the latest 40 public posts (spanning ~263 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (31) · French (4) · Russian (3) · Dutch (1) · Portuguese (1)
Avg boosts / post: 0.5
Top of the latest posts
11 bytes. That's all it takes. A newly disclosed OpenSSL "HollowByte" flaw lets attackers trigger a Memory Exhaustion DoS during the TLS handshake, forcing vulnerable servers to allocate up to 131 KB of heap memory from just an 11-byte mali
"Just shell out to certbot from PHP" No. Here's an honest comparison of every PHP ACME client worth using in 2026. Features, code examples, and when to just use certbot anyway. #PHP #LetsEncrypt #ACME #TLS #WebSecurity #OpenSource #Laravel
libcryptsetup FIPS 140-3 Tested & Available with wolfCrypt FIPS https://www.wolfssl.com/libcryptsetup-fips-140-3-tested-available-with-wolfcrypt-fips/ #wolfSSL #crypto #security #TLS
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/tls