I didn't need to allow oath that to read that. I have my browser configured like so https://github.com/gorhill/uMatrix/wiki/How-to-block-1st-par...
For that page all I had was: https://i.imgur.com/DQe8TIr.png you can clearly see oath was not enabled.
It would appear you do need to allow 1st-party JavaScript to allow the <script type="application/ld+json"> portion to load which contains the "articleBody": ....."
I am connected through my VPN, currently in NL, so yeah, GDPR.
If they don't offer an opt-out that is as easy as opt-in, I'm going to assume malign intent on the part of the site, and they can do without my traffic.
www.engadget.com -- script https://consent.cmp.oath.com/cmp.js 3p
www.engadget.com -- script https://consent.cmp.oath.com/cmpStub.min.js 3p
> Sure, I know there are ways I could work around it. But I shouldn't have to.Sadly that's the world we live in.
> It's supposed to be easy for a visitor to refuse consent for all that unnecessary tracking - which has no justification in terms of legitimate interest for the purpose of publishing a news article. It shouldn't require technical countermeasures (that 99% of users will not understand).
It shouldn't yet, it does .
> If they don't offer an opt-out that is as easy as opt-in, I'm going to assume malign intent on the part of the site, and they can do without my traffic.
With media that's a pretty safe assumption.
They searched for the wrong face into facial recognition software ... which did it's job perfectly.
This is akin to the police arresting someone because their name matched a name a criminal left behind. Happens all the time, and I'm sure that more than a few wrongful convictions happen this way. This is 99% the fault of the police.
Perhaps there's an argument that facial ID lowers the bar slightly for this to happen, but that's about it. When push comes to shove, neither Apple, nor the police did their work properly before resorting to heavy handed tactics ...