As if this would change anything.<p>The idea of third party cookies being bad is a reflection of the current state, not a methodology.<p>What happens if third party cookies are blocked?<p>Websites will just add a CNAME entry that points to whatever service they were using before. Then it's a second party (subdomain) cookie.<p>We need a different methodology how to keep cookies but limit their lifetime, reach, and damage they can do for its users, and a better unified authentication method that can also be spoofed/faked if websites become hostile. They need to be sandboxed, per URL scopes, not per domain.<p>We need to change the way of thinking of trust. Don't trust any website by default, only trust it once the user regularly visits it, or maybe set an allowed cookie lifetime per website after the user logs in.<p>But the current way of thinking about this problem led to the shithole that is XSS, session stealing and everything related to it.<p>Source: attempted to build my own browser that wanted to fix this and eventually had to give up