What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether the uniqueness ratio is meaningful when most variables match other similar devices.From this comment
- How realistic the reported uniqueness figure is, given it stays fixed across many browsers including Tor.From this comment
- Whether this code was produced by prompting a model rather than written deliberately.From this comment
- What data ad networks actually hold on individuals, like interests, location, and health.From this comment
- How much browsing history and personal habits large platforms retain on file.From this comment
What they doubted or pushed back on our summary
- The fingerprint identifier changes on each reload, suggesting too much unstable sampling.From this comment
- The identifier shifts every reload on Android Chrome, making it weak as a fingerprint.From this comment
- A useful fingerprint should recognise the same person across browsers and devices, not just one refresh.From this comment
- No ordinary user cares about fingerprinting warnings, which limits such tools.From this comment
What the maker answered our summary
5 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- The author says raw dumps are useless without a large representative population to compare against.From this comment
- The author admits including volatile features like canvas and audio was a mistake for a stable fingerprint.From this comment
- The overall fingerprint identifier is a hash of all the collected fields.From this comment
What a builder can take from it: Use only stable, consistent characteristics in a fingerprint and compare results against a real population before claiming uniqueness. our reading
The title, taken apart our calculation
This post got 275 points; the median for all 1442 posts is 112.
When it was posted our calculation
Monday at 18:00 UTC. Of 2,649 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 84 (3.2%) reached 50 points; on Mondays it was 3.1% of 7,396. The average over all hours is 2.9%. One post's time does not explain its result; the full table of hours is on the Show HN hub.
Check your title our calculation
Type the title you plan to post. It is compared with 1,442 Show HN posts that reached 50 or more points: its length, its shape, and how posts of that length and shape did. Nothing is sent anywhere.
Type a title above to see where it sits.
Draft my Show HN post
Paste your site address and get title options and a first comment for your own Show HN post, written from what your site says and checked against the numbers above. Nothing is posted for you.
Free to try and no account needed. FoxPlug is for people who ship several projects and keep stalling on telling anyone: it turns what you ship into posts you approve before anything goes out. See what each plan includes.
More teardowns
Points, comments, titles and times are Hacker News's own numbers, read from the post itself, last updated Nov 2026. Summaries of what people said are ours, written in our own words, and each one links to the comment it came from. Percentages and medians marked "our calculation" are computed from the posts counted on the page: they describe what happened, not what will happen to your post. FoxPlug posts nothing for you. Plans and limits are on the pricing page. Questions: support.
After the launch post: a changelog your users read
A launch brings visitors once. FoxPlug turns what you ship afterwards into a public changelog and ready posts, so the next visitor finds something new.
Start your changelog See a SaaS changelog example
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Visual cards and walkthrough videos made from what you shipped
- Posts for X, LinkedIn and dev.to written from your changes
- Connect GitHub and the tools you build with