4 ms·
What Kiss does is explicitly violating user intent -- ethical people assume that when cookies go away, the user is making a decision. From the paper summary :
by earl 15y ago
What Kiss does is explicitly violating user intent -- ethical people assume that when cookies go away, the user is making a decision.
From the paper summary : "The cache cookie method used ETags, and is capable of unique tracking even where all cookies are blocked by the user and “Private Browsing Mode” is enabled." Resuscitating cookies the user has cleared is simply wrong.
And you have an expansive definition of "ethical".
- mrkurt 15y agoCookies disappear all the time for reasons that have nothing to do with users nuking them. Users rarely delete their cookies, a vanishing cookie isn't an obvious indicator of privacy concerns. I should caveat this by saying that I wouldn't use an evercookie, though. While most vanishing cookies aren't privacy related, it's clear that a few are. We avoid all sorts of behaviors on the web to keep from treading on a few toes.
- cHalgan 15y agoCan you please elaborate this statement that "Cookies disappear all the time for reasons that have nothing to do with users nuking them"? I'm genuinely interested to understand in which cases cookies disappear. EDIT: But it is possible to detect case when cookies are intentionally deleted. Correct?
- mrkurt 15y agoSure. It's common for server or client side scripts to overwrite cookies, or cookie expirations. When you embed something that depends on cookies in a third party site, you have very little you can do to keep the site owner from nuking it unintentionally. Browsers frequently eat cookies for no good reason. Safari has been the biggest offender in my experience, but I've seen it in several. These are two really common issues I've personally dealt with, I know there are more but I can't think of them off the top of my head. EDIT: No, I'm not aware of any way to detect how/why a cookie has been deleted. It just vanishes.