• NekuSoul
    link
    fedilink
    English
    2201 month ago

    Recall won’t take snapshots of […] DRM-protected content.

    At least the movie industry will survive this unscathed. Thanks Microsoft. 👍

    • @cmgvd3lw@discuss.tchncs.de
      link
      fedilink
      English
      21
      edit-2
      1 month ago

      If its processed locally and sent nowhere, why is this a concern? Unless otherwise.

      Edit: I phrased it wrong. If MS claims its processed locally, and is like a second eye, why they would provide an exception to DRM contents. This could mean that some data might get sent to MS servers and transfer of DRM content is banned, this poses a legal risk. Who knows.

      • @Squizzy@lemmy.world
        link
        fedilink
        English
        311 month ago

        Because I absolutely do not trust microsoft to not have some information going back to a server somewhere.

        • Skua
          link
          fedilink
          30
          edit-2
          1 month ago

          I think you’ve misunderstood the comment above. They’re asking why snapshotting DRM-protected content would be a problem if everything stays local, implying that since it’s a problem it does not stay local

      • NekuSoul
        link
        fedilink
        English
        131 month ago

        The non-fun answer is that they’re most likely just using the default screenshot mechanism, which already blocks that. Other programs like KeePassXC, which also hides itself from screenshots and recordings (unless allowed) will probably not be included either.

    • @morbidcactus@lemmy.ca
      link
      fedilink
      English
      41 month ago

      KeepassXC seems to register as DRM protected content (I think…) for me, kills moonlight streams while it’s up so at the very least using a password manager (which you already should be using) would be protected?

      I already daily drive debian on my lab computer and laptop, guest I’ll be swapping my desktop over in the not to distant future…