IdeaWell

Project ideas from Hacker News discussions.

Show HN: GlassBox – what the browser reveals, and how identifiable you are

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Theme 1 – Privacy unease and the desire for a cleaner web
Many commenters expressed discomfort with how much browsers reveal and called for a fundamentally different model.
- bravoetch: “It's horrifying to see that our browsers give up anything at all. I feel like we need a new model where we just get served the content, and we don't serve up anything to the content provider. I feel ill.”
- jszymborski: “I just downloaded a fresh install of LibreWolf to test this and it did indeed have a stable UUID for me at 1/62E6… Fonts and Audio fingerprinting seems to be where a lot of the entropy is coming from… it is very discouraging.”

Theme 2 – Skepticism about the accuracy and completeness of fingerprinting estimates
Several users pointed out that the tool’s numbers can be skewed by anti‑fingerprinting measures or simply incorrect readings.
- dd8601fn: “This doesn’t seem right. 1 in 6.2 billion for Firefox on an iphone, not including ip/network uniqueness? Seems more plausible that anti‑fingerprinting is throwing it off?”
- mattkrause: “Some of the data seems straight‑up wrong. I know this computer has more RAM than reported and it's definitely not on a 4G network either.”
- daveoc64: “The APIs it's relying on to show you that information do implement some anti‑fingerprinting mechanisms - things like available memory will be put into rough buckets rather than returning the exact amount you have.”

Theme 3 – Ideas and practices for reducing fingerprintability
Commenters discussed ways to make fingerprints less stable or unique, ranging from network tricks to deliberate randomization.
- RandomBK: “It's worth noting that you need both uniqueness and some form of stability. If you consistently show up as a different fingerprint every time you visit or for every different site, then that is a form of privacy as well.”
- keito (on IPv6): “With IPv6… the right part identifies your specific device. But in most OSes the right part is randomly generated and changes on some cadence (e.g. daily).”
- ZihengQin: “Interesting work! Would randomnize the least frequent used fonts, apis and settings be an way to anti‑fingerprinting?”

🚀 Project Ideas

Generating project ideas…

FingerprintDB: Community Fingerprint Probe Repository

Summary

  • A collaborative, version‑controlled catalog of browser fingerprinting probes (canvas, WebGL, audio, fonts, etc.) that anyone can submit, test, and run locally.
  • Core value proposition: gives developers and privacy researchers a single, up‑to‑date source of fingerprinting vectors to audit their own browsers or build better anti‑detect tools.

Details

Key Value
Target Audience Privacy researchers, web developers, anti‑fraud engineers
Core Feature Web‑based UI to browse, search, and execute probes; Git‑backed contribution workflow
Tech Stack React, Vite, IndexedDB for local probe storage, GitHub API for contributions, WebAssembly for heavy probes
Difficulty Medium
Monetization Hobby

Notes

  • HN users complained about missing vectors and wanted “all of them in one place” (tke248: “I wanted to see all of them in one place, running against my own browser”).
  • Provides a practical utility for discussion: new probes can be vetted by the community, spawning threads on novel techniques.

FingerprintRarity: Privacy‑Preserving Crowdsourced Rarity Estimator

Summary

  • Collects only locally‑computed, irreversible hashes of a user’s fingerprint to build a real‑world distribution without sending raw data.
  • Core value proposition: replaces the entropy‑sum estimate with a true rarity score based on actual population frequencies, addressing concerns about inaccurate identifiability numbers.

Details

Key Value
Target Audience Privacy‑conscious users, security researchers
Core Feature Client‑side hashing (e.g., SHA‑3 of concatenated probe values) and optional upload of hash to a central aggregate server; server returns rarity percentile
Tech Stack Rust/Wasm for hashing, Svelte frontend, Go backend with Redis/HLL for cardinality estimation, Cloudflare Workers for edge
Difficulty High
Monetization Revenue-ready: Freemium (free basic rarity, paid API for detailed reports & historical tracking)

Notes

  • Users noted that GlassBox’s identifiability number is “an honest model, not a measurement” and wanted real population numbers (tke248: “For real population numbers, Cover Your Tracks and AmIUnique have the datasets”).
  • Enables discussion on how rare a fingerprint truly is, and can be integrated into existing fingerprinting tools for better transparency.

AntiFP Advisor: Personalized Anti‑Fingerprinting Coach

Summary

  • Browser extension that analyzes your current fingerprint, cross‑references it with a guide of mitigation techniques, and suggests concrete actions (e.g., disable WebGL, spoof canvas, randomize fonts) with one‑click apply.
  • Core value proposition: turns the overwhelming list of fingerprinting vectors into a prioritized, actionable privacy‑hardening plan.

Details

Key Value
Target Audience Everyday privacy‑concerned users, Tor/LibreWolf users
Core Feature Fingerprint scan (using existing probes), recommendation engine, optional toggle‑based spoofers for high‑impact attributes
Tech Stack Manifest V3 extension (TypeScript), uses Web APIs for probing, stores settings in chrome.storage, optional native host for font spoofing
Difficulty Medium
Monetization Hobby

Notes

  • Commenters expressed frustration about not knowing what to do (jszymborski: “I’m not sure what to do to be honest about this, it is very discouraging”) and sought a guide to lower fingerprint.
  • Provides practical utility: users can immediately see which changes reduce their identifiability score, fostering discussion on effectiveness of various mitigations.

Read Later