Re:US reportedly investigate claims that Meta can read encry...
by willis936 on Saturday January 31, 2026 @10:24AM
(#46837450)
By avoiding untrustworthy clients. All Windows devices should be considered compromised after last year.
[ Parent
| on HN ]
Re:US reportedly investigate claims that Meta can read encry...
by Retr0id on Saturday January 31, 2026 @10:25AM
(#46837459)
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.
Re:US reportedly investigate claims that Meta can read encry...
by willis936 on Saturday January 31, 2026 @10:32AM
(#46837516)
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.
Re:US reportedly investigate claims that Meta can read encry...
by Retr0id on Saturday January 31, 2026 @10:34AM
(#46837534)
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."
Re:US reportedly investigate claims that Meta can read encry...
by cobertos on Saturday January 31, 2026 @10:36AM
(#46837553)
Windows has been sending usage history back to their servers for longer than just last year
Re:US reportedly investigate claims that Meta can read encry...
by GraemeMeyer on Saturday January 31, 2026 @10:31AM
(#46837508)
Why last year?
Re:US reportedly investigate claims that Meta can read encry...
by willis936 on Saturday January 31, 2026 @10:35AM
(#46837545)
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.