#資料壓縮
Live, measured metrics for the hashtag #資料壓縮 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #資料壓縮
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 · mastodon.online (Mastodon public tags API) · fetched 2026-08-21 23:27 UTC1 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-08-21 23:27 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-08-21 23:27 UTCEverything below is measured over the latest 20 public posts (spanning ~26016 hours).
Posting hours (UTC) — busiest: 12:00
Languages: Chinese (Taiwan) (19) · Chinese (1)
Avg boosts / post: 0
Top of the latest posts
🌖 GitHub - RyanCodrai/turbovec:基於 TurboQuant 並以 Rust 編寫提供 Python 綁定的向量索引工具 ➤ 打造極速輕量化的本地向量檢索:TurboQuant 演算法的 Rust 實踐 ✤ https://github.com/RyanCodrai/turbovec turbovec 是一款高效能的向量索引庫,採用 Google 研究的 TurboQuant 演算法,能在大幅降低記憶體需求的同時保持極速檢索。它成功將 1000
🌗 如何將三進制數壓縮至 8 位元組中 ➤ 高效能三進制數據的封裝與 SIMD 解碼策略 ✤ https://compilade.net/blog/ternary-packing 本文探討瞭如何將三進制數(trits,值為 -1, 0, 1)高效率地封裝進 8 位元位元組(bytes)中。作者發現 5 個三進制位(5 trits)可精準填入 243 個組合(小於 256),其資訊密度高達 99.06%。為了實現硬體友好的高效解碼,作者捨棄了傳統除法與取模運算,改採用定點數乘
🌗 極致緩慢的 DEFLATE 13 級壓縮技術解析 ➤ 以算力換取極致壓縮比:libdeflate 的實驗性進化 ✤ https://kirill.korins.ky/articles/hellishly-slow-level-13-deflate-compression/ DEFLATE 壓縮格式因其廣泛的兼容性,至今仍是網路傳輸與封存的標準。Kirill A. Korinsky 在其研究中引入了極致的「13 級」壓縮層級,這一層級並非為了日常運作設計,而是專為「一次壓
#資料壓縮 across platforms
every network with a public tag surfaceFollow #資料壓縮 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/資料壓縮