It's sad that Safari does this, especially considering there's a work around using POST: https://gist.github.com/586182 -- it translates to complexity and has performance hit, and doesn't actually add security.
Rather than allowing it because of this, wouldn't it be better to remove this method. I kind of like the balance without the 3rd party cookies, I can write a 3rd party script that people include on there website which stores cookies on their own domain. From the point of view of a single website this is good, from the point of view of a network of websites and those that want to advertise on all of them I guess it is bad. Can always base things off IP, not as good but a similar effect.
Don't imagine for a second that a browser policy change like this would do anything but increase the value and use of cookieless tracking by content delivery networks.
Well its really only from an advertising perspective, the advertiser and the network. From the end users perspective they get the choice, if they really want targeted ads they can always turn the third party cookies on.
Target the ad based on the site the user is visiting, not on trying to violate the user's privacy. On a site to do with cars, show car ads. On a site to do with Dell, show Dell ads.
It's not frickin' rocket surgery.
If no one has a site relevant to your ads, there's your hint that no one wants your service/product. If you believe that I'm wrong... start one. Make a site relevant to that interest, and then you can on-sell your product. Build/find the community that believes in the same stuff you do, and engage them.
