> Not all cookies are used for tracking.
No, but third-party cookies are basically used for tracking. A legitimate site does not depend on a third-party cookie to handle features or login. At all, full stop no ifs, ands, or buts.
> Be prepared to start losing your settings in web apps or being logged out after 24 hours if you use Safari.
Again, not going to happen because those are not associated with third-party cookies.
> They're deliberately trying to hold back web technology so that people will be forced to create and use native apps instead.
God no, or there would be no icloud.com, online shopping app, or their other web offerings. There is no conspiracy or holding back, this is purely to protect the user.
> I say this as a die-hard MacBook user.
Then you should be prepared with more research and have your homework done ahead of time on this matter. This is all nonsense and just false.
Sites which use Disqus, or similar, for comments.
I hate Disqus with a passion and wish horrible flaming death upon it, and am actually quite pleased that this will break it. But nonetheless it's a "legit" use of third-party cookies to provide a feature (remembering login on an embedded commenting engine).
http://benalman.com/code/projects/jquery-postmessage/example...
I mostly just ignore it, why do you hate it with such intensity? hahah
I'd point out that in the case of DocuSign signing sessions powered by iframes that without being able to set this third party cookie prevents the session from loading. Probably the only use case of a third party cookie being useful that I can think of.
After reading the webkit blog post on ITP I had no idea they changed this, but yeah, they are probably going to anyway if haven't yet. Otherwise it'd be too easy game this.
Apple wasn’t the one that broke the “functionality” of cookies. Though I’ll allow that one could think that third-party tracking cookies were part of the original intent.
Be prepared to start losing your settings in web apps or being logged out after 24 hours if you use Safari.
Be prepared to start reading articles on how this actually works before sharpening the pitchfork. I’ll give you a hint: none of what you describe will come to pass.
If that was the intent they wouldn't have already killed the native APIs for device identifiers ages ago.
What's more, the claim that Apple is doing this for the sake of user trust is a lie. The real reason they're breaking the functionality of cookies is the same reason they refuse to implement progressive web apps, and the same reason they've become the slowest browser to adopt new standards, and the same reason you see "Safari is the new IE" all over the place. They're deliberately trying to hold back web technology so that people will be forced to create and use native apps instead. They're desperately trying to cling to the annual developer license fees and app commissions.
I say this as a die-hard MacBook user. I prefer Apple to Microsoft, but I hope Google wins in the web-vs-native holy war.