> maybe they've just got better over time at not relying on cookies for things they shouldn't?
It may be that. I just tried and Twitter is working perfectly without third-party cookies. Some months ago it didn't allow me to login.
With Google I had a similar problem, I couldn't login into my Google Account in sites that weren't the search engine (Docs, YouTube, etc). I just tried them, and again, it seems that it works now.
I use Chrome stable. Maybe something changed in the management of third-party cookies in recent releases?
Safari help says "Select to reject cookies from advertisers and from “third parties”—websites other than those you open. This might help prevent certain advertisers from storing cookies on your computer."
This might mean that they reject third-party cookies from being set, but not from being read. That is, once you get a cookie (e.g. signed in to Facebook), every other request to Facebook (even if it's through the "Like" button) will also send your cookie.
The flag that appeared in the latest Chrome beta specifically disables sending of cookies to third parties, even if you have them.
Comments
> maybe they've just got better over time at not relying on cookies for things they shouldn't?
It may be that. I just tried and Twitter is working perfectly without third-party cookies. Some months ago it didn't allow me to login.
With Google I had a similar problem, I couldn't login into my Google Account in sites that weren't the search engine (Docs, YouTube, etc). I just tried them, and again, it seems that it works now.
I use Chrome stable. Maybe something changed in the management of third-party cookies in recent releases?
I would suspect it has something to do with Safari (Mobile at least) having third party cookies disabled by default.
Safari help says "Select to reject cookies from advertisers and from “third parties”—websites other than those you open. This might help prevent certain advertisers from storing cookies on your computer."
This might mean that they reject third-party cookies from being set, but not from being read. That is, once you get a cookie (e.g. signed in to Facebook), every other request to Facebook (even if it's through the "Like" button) will also send your cookie.
The flag that appeared in the latest Chrome beta specifically disables sending of cookies to third parties, even if you have them.