The article is literally about blocking third party cookies by default. They also introduced some other things, but before the release in that article, they wer

The article is literally about blocking third party cookies by default. They also introduced some other things, but before the release in that article, they were not blocking third party cookies by default. In Safari, if you loaded a pixel from https://advertiser.com/resource https://advertiser.com/resource that was referenced on different sites, advertiser.com would get the same cookie. This is still true. What blocking third party cookies means is that advertiser.com can't set a cookie when its pixel is loaded from another website. Safari didn't even think to implement it until Chrome announced that they would do it and worked with web publishers to migrate away. As far as sending cookies to a different origin, Safari didn't even support the SameSite attribute until 2019, three years after Chrome and one year after Firefox. It's not for nothing that Safari gained its reputation for being slow at adopting web standards.