The main difference from what I understand is that with Apple's system, if you did not have a token, you could still access the content. This is the opposite of what Google proposes which is to only serve the content to devices with the token, hence the backlash. It's play along or no internet for you.
Google's proposal also has sites serve content to clients without the attestation, or at least so they claim in the repo (thus the proposal to make the check deliberately fail sometimes, so websites won't rely on it. Of course, there is no guarantee it will stay that way, Google could change that policy whenever they want.
The main difference is really in Google's dominance on the web. Sites can't start requiring Safari, but they can start requiring Chrome or Safari.
Interesting article, I for sure didn’t noticed it.
I think that the tech behind this is quite interesting and useful, that is not the issue. The issue is, in my opinion, that the party that attests you are trusted is a firm like Apple, Google, or Microsoft. With all the antitrust implications of that.
Now we as a society need to make a decision, do we want to use this tech to make certain parts of the web more safe? And do we want to place that responsibility in the hands of firms, or should we want a government to pick up that responsibility?
I'm not sure I follow you. The article only mentions that Apple launched a similar DRM last year and that's about it, nothing to do with anti-trust laws.
I read this headline when I was half asleep at 4am and somehow understood it to mean Apple was firing back at Google. But no... completely the opposite. Goddammit.