Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Seems a bit much, but k-anonymity could work here. Hash the domain, take the prefix, get a batch of favicons back. They won’t know which you visited, but still get the benefits of consistent favicon support.


And how would they get the "batch of favicons" in the first place?


When there's a miss, send the domain to the server so that it can fill the cache. You probably won't even have to do that as DDG could have already filled the cache with their search results.


OK, at what point does it become complicated enough to just implement that shit client side? :-)


That's an elegant fix, but for a problem that wouldn't exist if the feature was properly designed. (IOW, designed as a local function.)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: