#x25519kyber768
Live, measured metrics for the hashtag #x25519kyber768 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #x25519kyber768
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 · mas.to (Mastodon public tags API) · fetched 2026-08-01 09:16 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-08-01 09:16 UTCNo related tags with measured usage found for #x25519kyber768.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-08-01 09:16 UTCEverything below is measured over the latest 3 public posts (spanning ~8437 hours).
Posting hours (UTC)
Languages: Russian (1) · Chinese (1) · Japanese (1)
Avg boosts / post: 1
Top of the latest posts
Постквантовый TLS внедряют уже сейчас Квантовый компьютер, который будет решать криптографические задачи (cryptographically-relevant quantum computer или CRQC в терминологии АНБ ), пока далёк от реальности. Но проблема в том, что создатели
Chrome 124 啟用了 X25519Kyber768 在「Google Chrome's new post-quantum cryptography may break TLS connections」這邊看到的，出自「Q1 2024 Summary from Chrome Security」這邊的公告。 Chrome 124 預設啟用 X25519Kyber768 了： After sev https://blog.gslin.org/archives/2024/04
「 #TLS #セキュリティ の強化: #Google、#Chrome 116 に耐量子暗号化を追加」： The Hacker News 「グーグルは、Chromeブラウザのバージョン116から、#量子抵抗暗号アルゴリズム のサポートを追加する計画を発表した。 「Chromeは、TLS で対称暗号を確立するために #X25519Kyber768 のサポートをChrome 116から開始します。 Kyberは、量子コンピューティングの出現によってもたらされる将来のサイバー攻撃に
#x25519kyber768 across platforms
every network with a public tag surfaceFollow #x25519kyber768 straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/x25519kyber768