https://fingerprint.com/blog/ios15-icloud-private-relay-vuln...
> 3rd party cookie blocking?
It's very funny that you should ask this question in response to an article about fingerprinting without cookies.
But yes, there are various workaround to use 1st party cookies or other storage to take the place of 3rd party cookies.
Perhaps the worst is the Safari "Privacy Report", which has always been misleading: https://www.simoahava.com/privacy/intelligent-tracking-preve...
https://www.schneier.com/blog/archives/2009/11/beyond_securi...
Public Relay is obviously not accurately described by that term and any rule which classifies it as such would be useless because it would classify all browser security as theater because everyone has had bugs, and everyone has had to adopt more sophisticated defenses to counter more sophisticated attackers.
I’d say the privacy report is the only real false security feature, but Apple was a laggard in that market. For all we know, they could have been trying to match features with Ghostery or Brave that teach consumers this is a feature you should expect from your browser. Users may also have been needed education about that behavior in order to justify the compatibility regressions cookie blocking incurs. It’s impossible to know from the outside, but your body of evidence to support a really strong accusation is quite weak.
If Safari behaved the same as Chrome, then Apple couldn't market Safari as more private than Chrome.
I don't know what you're talking about. What are X, Y, and Z specifically?
All software has bugs. I think it is more interesting to see how companies respond to reported issues. And how they improve things.
Is OpenSSL "theatre" because it had (bad!) bugs in the past?