3 ms·
> the company hoped to phase out third-party cookies in Chrome once it could meet the needs of both users and advertisers. Chrome, the browser, can't change ho
by 8organicbits 6y ago
> the company hoped to phase out third-party cookies in Chrome once it could meet the needs of both users and advertisers.
Chrome, the browser, can't change how web servers are implemented. Users needs are met as long as web servers behave as they should. I've disabled 3rd party cookies and haven't seen any issues (I'd suggest others try it as well).
I suspect mostly advertisers are affected at this point.
If this becomes a thing, I'll block it in my browser.
- michaelt 6y agoI do the same - there are a number of Google properties that get broken. Usually because they try to provide named-users-only access to user-generated content, then exile user-generated content to other domains (like googleusercontent.com ) and one can't be logged in on the other domain without cookies. I've filed bugs with Google about this behaviour, and had them accepted as valid, but they don't seem in a hurry to fix them - I assume because third-party tracking is google's core business.