Comment on Microsoft’s Recall feature is still threat to privacy despite recent tweaks

NaibofTabr@infosec.pub ⁨3⁩ ⁨weeks⁩ ago

• Zagorath@aussie.zone ⁨3⁩ ⁨weeks⁩ ago

  One could argue that it’s a feature that could be done on-client without sending to a server. Or with its server component doing nothing more than syncing with E2E encryption.

  source

  • russjr08@bitforged.space ⁨3⁩ ⁨weeks⁩ ago

    I have zero interest in Recall, but I thought it was already done on-device? IIRC it always was that way, which is why it’s only available on new computers containing dedicated “neural coprocessors” I believe was the term.

    Now given that it’s closed source, you have to trust that they aren’t silently sending data back to themselves - which is where my problem lies, I don’t trust them in the slightest.

    source

    • sugar_in_your_tea@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

      You can verify that nothing is being sent back by watching network traffic. I guess they could hide it in update packets, but thats pretty unlikely.

      source
    • Zagorath@aussie.zone ⁨3⁩ ⁨weeks⁩ ago

      I’ll admit I’ve not looked into it. My computer won’t even upgrade to Windows 11 if I wanted it to, thanks to MS’s artificial restriction on compatibility. Maybe it is all on-device. But if so, whence all the privacy complaints? And does it not allow syncing between devices?

      source

      • FreedomAdvocate@lemmy.net.au ⁨2⁩ ⁨weeks⁩ ago

        So you don’t even know and didn’t bother to check if it is on-device before attacking it for not being on-device?

        source
  • FreedomAdvocate@lemmy.net.au ⁨2⁩ ⁨weeks⁩ ago

    Recall is done on-client.

    source