Retr0id 19 hours ago

That's not mitigating client compromise, that's a whole other thing - trying to construct an uncompromiseable client.

You don't build defense-in-depth by assuming something can't be compromised.

  • willis936 19 hours ago

    Clients can always be compromised. I'm not talking about a client that can't be compromised, but simply a client that is not compromised out-of-the-box.

    • Retr0id 19 hours ago

      That seems orthogonal to the subject of this discussion, i.e. "Compromise of the client side application or OS shouldn't break the security model."

cobertos 19 hours ago

Windows has been sending usage history back to their servers for longer than just last year

GraemeMeyer 19 hours ago

Why last year?

  • willis936 19 hours ago

    Windows recall, intrusive addition of AI features (is there even a pinky promise that they're not training on user data?), more builtin ads, and less user control (most notably the removal of using the OS without an account - something that makes sense in the context of undisclosed theft of private information).

    This was 2025. I'm excited for what 2026 will bring. Things are moving fast indeed.