I use a browser that does not support favicon Wondering why users of popular browsers believe favicon is needed (I'm assuming users asked the authors of those browsers for favicon)
Supercookie: Browser Fingerprinting via Favicon (2021)
71–80 of 105 posts
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#72People actually wrote READMEs / commit messages like that before? Have I been living under a rock?
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#73At some point we need actual consequences for sites that intentionally hide their tracking. It should be criminal. It is stalking and has real world consequences. Just because an exploit exists doesn't mean it should be used. That logic is like saying it is OK to break into a house because the lock on the door was weak. If we don't get real protections, at what point does it become justified to go offensive against s…
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#74I use a browser that does not support favicon Wondering why 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
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#75Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#76At some point we need actual consequences for sites that intentionally hide their tracking. It should be criminal. It is stalking and has real world consequences. Just because an exploit exists doesn't mean it should be used. That logic is like saying it is OK to break into a house because the lock on the door was weak. If we don't get real protections, at what point does it become justified to go offensive against s…
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#77At some point we need actual consequences for sites that intentionally hide their tracking. It should be criminal. It is stalking and has real world consequences. Just because an exploit exists doesn't mean it should be used. That logic is like saying it is OK to break into a house because the lock on the door was weak. If we don't get real protections, at what point does it become justified to go offensive against s…
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#78At some point we need actual consequences for sites that intentionally hide their tracking. It should be criminal. It is stalking and has real world consequences. Just because an exploit exists doesn't mean it should be used. That logic is like saying it is OK to break into a house because the lock on the door was weak. If we don't get real protections, at what point does it become justified to go offensive against s…
If you visit my eg. physical clothing store I'm allowed to monitor your in-shop behavior to better optimize my store for your needs. Same for a restaurant etc. That's how _you_ get _much improved services_ and I get _happier customers_. 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_ c…
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.
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#79I was sure this has been a thing for a while, either that or safari has a UI bug since forever. I regularly get the wrong favicon in specific sites, for example ars technica favicon in reddit
My hacker news icon has been stuck as the icon for a weather site that I sometimes check. It’s been stuck that way for close to a year now, and has survived an iOS update too. It persists across profiles and into private browsing mode.
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#80Totally unrelated, but what I found interesting: the README hasn’t been touched for years, yet it looks entirely AI generated. Including the commits. 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 (Edit: It's 20, misread) year old I'm not too surprised that it's a bit unusual compared to others.