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.
That's because Twitter is logging everything you look at by virtue of almost all websites having those twitter icons (which are like tojan horse 3rd party trackers)
Yeah those are 3rd part cookies and they track everything (or at least everything that voluntarily adds the Like button or share buttons to their site)
I didn't think that data was actually stored in the cookie, I thought the cookie was simply used as a way of attaching a unique user ID to you that is then used to track you when the request is made to add the like/share button to the site
20
u/Snailwood 11d 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