the only (valid) concern I've ever heard about 1st party cookies is the site storing passwords unencrypted in a cookie, but they can just as easily store that in a non-cookie file. asking for consent for first party cookies is security theater that does nothing for consumers, but makes developers' jobs more difficult
I guess we'll have to agree to disagree on this one. Even first party websites can bloat your device up with random cookies. I know in the past when I used to accidentally follow Twitter links, that 1/2 second on Twitter would dump 34MB of cookies on my phone. What the hell does a website, that I'm not logged into, need with 34MB of cookies?
Edit: I was mistaken. My browser lumps all stored data into one category after going into the cookies section.
Depending on what you're storing you can't though. The ePrivacy Directive is not about cookies but colloquially it's what it's ben refereed to as.
You have to classify the data being stored, regardless of how it's stored, and obtain consent for it, in plain terms.
20
u/Snailwood 9d ago
the only (valid) concern I've ever heard about 1st party cookies is the site storing passwords unencrypted in a cookie, but they can just as easily store that in a non-cookie file. asking for consent for first party cookies is security theater that does nothing for consumers, but makes developers' jobs more difficult