Supercookie: Browser Fingerprinting via Favicon (2021)
Mood
thoughtful
Sentiment
mixed
Category
tech
Key topics
browser fingerprinting
online tracking
privacy
The 'supercookie' technique uses favicon caching to track users across websites, sparking discussion on browser security, online tracking, and the need for stronger privacy protections.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
7h
Peak period
39
Day 1
Avg / period
20
Based on 40 loaded comments
Key moments
- 01Story posted
11/16/2025, 7:39:52 PM
2d ago
Step 01 - 02First comment
11/17/2025, 3:09:30 AM
7h after posting
Step 02 - 03Peak activity
39 comments in Day 1
Hottest window of the conversation
Step 03 - 04Latest activity
11/17/2025, 8:08:59 PM
1d ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Rename thumbnail to favicon: https://github.com/brave/brave-core/commits/master/patches/c...
Then abandoned in favor of Chromium including favicons in the regular cache https://news.ycombinator.com/item?id=45954466
Quick side note here. I appreciate the research calling this out. We need to know the dangers out there to figure out how to protect ourselves, especially since governments don't seem to take this seriously.
Old business model: solve a problem for your customer, add some value, take home a cut. Current business model: solve investment return for your investors, get the returns by addicting your end-user to something they don't need. Future business model: ?
I don't see how that's related? Anyone looking to increase their revenue looks at tracking. Even I, with my popular open source projects, receive emails to add tracking, let alone business that need money to pay their employees.
Ofc I'm not allowed to freaking resell that data. THIS is the problem in online: releseling and data-brokers. Just KILL these categories of businesses off completely and make _them_ criminal (like even give f prison sentences to them).
We should get back to our sanity in ONLINE. As long as you're on _my (online) property_ and using _my services_ I can of course see EVERYTHING you f do, and should stop pretending I don't. As long as I'm not sharing this data with anyone else, I should be 100% allowed to use every drop of this data to improve my services to you and totally differentiate myself from the incompetent competition that can't properly do this.
Data privacy (from EU's GDPR to... everything else) only helps big corporations fend-off competition from small startups of boutique shops that could easily out-compete them by offering hyper-personalized hand tailored micro-optimized experiences for their smaller number of customers based on the loads of data they collect from them.
...we've all been brainwashed by this privacy psyop to sheepishly "fight for our privacy" in ways that are detrimental to us and only help our corporate oligarch overlords maintains an even tighter grip on power, while offering us worse and worse services. Wake the f up, DATA IS MEANT TO BE USED to IMPROVE goods and services, not remain uncollected or sit unused!
That's fine, but you are not allowed to send me malware, that runs on _my property_ and snoops on _my data_.
Also data doesn't stop being mine, just because you have it. You also can't take photographs of random people and claim this is yours now. That's an important difference between the USA and European countries.
Now website code does typically run on your device, but I'd say that once you're a paid logged in user you clearly accepted to run it, under the conditions of it staying in its browser sandbox so... if you think it's "malware" then just stop being a customer. Otherwise software has a right to monitor its own operation.
I consider fingerprinting my browser, by running programs and measuring the timings and characteristics of the browser to be a side-channel attack on the browser sandbox.
> Otherwise software has a right to monitor its own operation.
If websites would only "monitor its own operation", we would hardly have any discussion.
> if you think it's "malware" then just stop being a customer.
Easier said than done, when >90% of websites do this. Show me a mainstream corporations website, that work without Javascript. You can hardly pay for a train ticket and make an appointment to government services, without these crap.
Also there must be some rules what software vendors are allowed to do, since the average user can hardly reverse-engineer all the websites they (need to) visit. This is what regulations like GDPR try to enforce.
> and re the photography example, afaik model release forms work similarly in the EU and US, right?
It's not about contracting a model, it's about doing a random photoshot in public. People have the right to their own picture here, irregardless of who takes that picture and who posses it.
Wondering why do users of popular browsers believe favicon is needed
(I'm assuming users asked the authors of those browsers for favicon)
This might be useful when switching from, e.g., tab#1 to tab#7, using keyboard shortcut Ctrl-7
People actually wrote READMEs / commit messages like that before? Have I been living under a rock?
Emoji-heavy documentation/commit messages always seem very popular in JS projects, as this is seems to be the project of a 12 year old I'm not too surprised that it's a bit unusual compared to others.
I knew this was part of the JS community, I just didn’t realize AI was literally 1:1 using the same style.
I guess didn’t realize that the NodeJS community was so dominant.
Or maybe is it because the NodeJS community always had a style of “many small libraries”, which causes them to be over represented?
Another interesting method for web fingerprinting explored by a team of researchers back in 2022 uses the GPU to create unique fingerprints and uses them for persistent web tracking. Codenamed 'DrawnApart' [1] and relies on WebGL to count the number and speed of the execution units in the GPU, measure the time needed to complete vertex renders, handle stall functions, and more. It uses short GLSL programs executed by the target GPU as part of the vertex shader to overcome the challenge of having random execution units handling the computations. Hence, the workload allocation is predictable and standardized.
__________
1. https://www.bleepingcomputer.com/news/security/researchers-u...
60 more comments available on Hacker News
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.