Conversation

twitter.com/BrendanEich/st I don't see how this isn't DRM, and it's not a good precedent. Web sites would love to use this kind of DRM to prevent users from blocking advertisements or other unwanted features exactly like Brave is doing, and Brave would be locked out by that too.

Quote Tweet

BrendanEich

@BrendanEich

Jul 25, 2019

Replying to @DanielMicay @justsee and @bcrypt

DRM is WideVine. OS-level antifraud is not "DRM" in any useful sense of the TLA. I think @EFF agrees, but anyway, your further "enforced viewing" words were inaccurate and misleading! You mean: we make Brave Ads viewers pass OS-tested antifraud that the appstores require. Yes.

Replying to

DRM is when there's a TEE in your device in which secret keys you don't own are used to decrypt content. Brave Ads don't do that. You abusing "DRM" would be like me calling you "adfraud apologist." What do you suggest if not the OS-level antifraud checks native apps use? Be real!

Daniel Micay

@DanielMicay

Replying to

@BrendanEich

SafetyNet does have support for using secret keys in the TEE or HSM via key attestation. It doesn't currently enforce that key attestation passes, which is why it's currently so easy to bypass, but that's clearly going to change. TEE doesn't need to decrypt it for it to be DRM.

11:43 PM · Jul 25, 2019Twitter Web App

Replying to

and

You can call it anti-fraud or anti-cheat but it's effectively same thing. It's enforcing rules about how the user can use the app / content. Brave is producing content (the site with different ads) and enforcing rules about the user should be able to use that content. It's DRM.

Replying to

Gotcha: "(the site with different ads)" is false. If you did know, you're lying. If you didn't, you are inexcusably ignorant. We do *not* replace ads in publisher pages.

Show replies