3 ms·

> All encryption is end-to-end, if you’re not picky about the ends. This reminds of how Apple iMessage is E2E encrypted, but Apple runs on-device content detec

> All encryption is end-to-end, if you’re not picky about the ends. This reminds of how Apple iMessage is E2E encrypted, but Apple runs on-device content detection that pings their servers, which you can't possibly even think of disabling. [1][2] [1] https://sneak.berlin/20230115/macos-scans-your-local-files-now/ https://sneak.berlin/20230115/macos-scans-your-local-files-n... [2] Investigation in Beeper/PyPush discord for iMessage spam blocking

saagarjha 9mo ago
What’s the concern here? The blog post you linked does not really support its claims with evidence.
- perching_aix 9mo ago
  They're actually two separate claims, one of which the blogpost does support. The other one is seemingly ought to be supported by some conversations on a Discord server. The concern is obvious though, not sure what's unclear about that: it's a bit pointless to have E2EE, if the adversary has full access to one of the ends anyways.
xvector 9mo ago
[1] is supposedly debunked: https://pawisoon.medium.com/debunked-the-truth-about-mediaanalysisd-and-apples-access-to-your-local-photos-on-macos-a42215e713d1 https://pawisoon.medium.com/debunked-the-truth-about-mediaan... > the network traffic sent and received by mediaanalysisd was found to be empty and appears to be a bug. I say "supposedly debunked" because empty traffic doesn't mean there's nothing going on. It could just be a file deemed safe. But then the author said: > The network call that raised concerns is a bug. Apple has since released macOS 13.2, which has fixed this issue, and the process no longer makes calls to Apple servers