• FreeloadingSponger@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    1 year ago

    I don’t really understand how that’s possible. The browser gets a token from the third party, and passes that token to the server to “prove” it’s running the DRM. The server then passes code back to the browser. At that point, why can’t the browser just cut out the DOM elements which are ads?

    I don’t understand how code I write on hardware I run locally can ever have it’s hands tied like this.

    • schroedingershat@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      It won’t be your hardware in a few years if this goes through. The code will run in a secure enclave and you won’t be able to access your bank or log in to government websites if you control the hardware.

      • 𝒍𝒆𝒎𝒂𝒏𝒏@lemmy.one
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Android phones are starting to do this, and it’s a nightmare for people like me who actually want to own the device they purchased.

        Needing root access on Android to regain basic functionality (such as the ability to backup installed apps) is a sad indicator of where we’re headed ☹️… As much as I dislike iOS’s walled garden, they make backups dirt easy for the end user - and they do complete backups too - app data, homescreen layout and all.

    • 133arc585@lemmy.ml
      link
      fedilink
      arrow-up
      2
      arrow-down
      2
      ·
      1 year ago

      I see what you’re saying. I read it as implying the browser would fake the attestation token. I don’t know the answer, but if their (stated) goal is to stop bots and scrapers, I have to assume it wouldn’t be so simple. After all, a lot of bots and scrapers are literally running an instance of Chrome.