#瀏覽器隱私
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 · fosstodon.org (Mastodon public tags API) · fetched 2026-08-26 10:33 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-08-26 10:33 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-08-26 10:33 UTCEverything below is measured over the latest 2 public posts (spanning ~357 hours).
Posting hours (UTC)
Languages: Chinese (Taiwan) (2)
Avg boosts / post: 0
Used together with
Top of the latest posts
🌖 Chrome 移除「裝置端 AI 不會傳送資料至 Google 伺服器」的保證聲明 ➤ 隱私透明度降級？AI 資料處理政策的潛在變動引發關注 ✤ https://old.reddit.com/r/chrome/comments/1t5qayz/chrome_removes_claim_of_ondevice_al_not_sending/ 近日有 Reddit 用戶指出，Google 在更新 Chrome 瀏覽器版本後（從 v147.0.7727.138 升級至 v14
🌕 發現 Firefox 穩定識別碼漏洞：所有 Tor 私密身分恐遭串連 ➤ 隱藏在資料庫排序中的隱私殺手：IndexedDB 實作瑕疵如何擊穿 Tor 的匿名防禦 ✤ https://fingerprint.com/blog/firefox-tor-indexeddb-privacy-vulnerability/ 安全研究人員近期發現 Firefox 及其衍生瀏覽器（如 Tor Browser）存在一項嚴重的隱私漏洞。該漏洞源於 IndexedDB API 在處理資料庫清
#瀏覽器隱私 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/瀏覽器隱私