3 ms·
That could be a tracking protection feature in Safari? https://news.ycombinator.com/item?id=26051370 https://news.ycombinator.com/item?id=26051370 The part whe
by capitainenemo 5y ago
That could be a tracking protection feature in Safari?
https://news.ycombinator.com/item?id=26051370 https://news.ycombinator.com/item?id=26051370
The part where the author files a bug to get caching "fixed" in Firefox is also interesting.
https://bugzilla.mozilla.org/show_bug.cgi?id=1618257 https://bugzilla.mozilla.org/show_bug.cgi?id=1618257
Edit... Sorry. Actually, I forgot how the abuse worked, it relies on persistent caching. So Firefox doesn't cache, preventing bookmark tracking. Safari aggressively caches, so would. Any amount of caching would be a problem.
Hm... unless Safari never checks for updates to the Favicon at all. That would defeat the exploit as well. So very aggressive caching with no check for updates, also good? Ok. I stand by my original guess :)
- samwillis 5y agoIf it's to prevent tracking I'm all for it, but I would love them to then provide an API to enable favicon overlays for badges/notifications (in a tracking abuse free way). Maybe, just maybe, with the news they are finally implementing Web Push Notifications and the suggestion it's the first step towards supporting PWAs, they might create a icon badge api for both the favicon but also PWA icons.
- SilasX 5y ago>That could be a tracking protection feature in Safari? Heh, that feels like the Web in a nutshell: Devs: "Hey, wouldn't it be convenient if we cached--" Advertisers: "Aha! Another means to track people!"
- soperj 5y agoClassic "that's not a bug that's a feature"