Lots of reasons to not use apple products if you care for privacy (github.com)

submitted 1 year ago by jogai_san@lemmy.world to c/privacyguides@lemmy.one

5 comments fedilink hide all child comments

top 5 comments

sorted by: hot top controversial new old

[-] starkle@lemmy.one 1 points 1 year ago

Only 5 of the bullets are related to privacy. The first two regard Apple's purported plans to implement client-side scanning, which have been paused and and don't presently exist. The third one was FUD that has been debunked. The fourth one has a broken link. The last one regards Apples tracking of iCloud account usage in their apps and services, which is totally optional at least on macOS.

There are plenty of reasons to avoid Apple, and this page lists several, but the privacy argument is not strong here.

[-] million@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

Here is the thing about the client side scanning, it was a way for them to fully encrypt iCloud while keeping law enforcement happy. In my mind it was a privacy win, as the alternative was to scan an unencrypted file in the cloud, much like Google, Microsoft, et al does.

Privacy isn't an absolute, there is a push pull with the other needs of a society, if folks legitimately think that CSAM isn't a problem then they have had a very sheltered internet experience.

I know this view is hugely unpopular with the privacy crowd but what Apple was doing honestly felt like a reasonable compromise to me. I guess it's moot because they now have an encrypted iCloud option without the client side scanning.

[-] alb@kbin.social 1 points 1 year ago

The problem is that client-side scanning has been demonstrated to be a big threat to security by scholars in the field of encryption. In addition, client-side scanning can be circumvented by criminals by modifying the hash of images; this is why its introduction caused a big outcry and Apple dropped its introduction.

[-] starchturrets@feddit.de 1 points 1 year ago

I think the reason it caused such an outcry was that it was a little more advanced than simply checking a hash, which could be defeated by cropping it or something similar.

[-] hemmes@lemmy.one 1 points 1 year ago

My sentiments as well. When they wouldn’t open that shooter’s phone for the government and were about to goto war right before the FBI got it done with Azimuth Security (discovering nothing after spending nearly a million dollars lol). You would think they said to themselves “we have to do something to get out of the cross hairs.” And like you said, they soon released full end to end encryption to close the gap (which I’ve done and highly recommend).

this post was submitted on 16 Jun 2023

2 points (100.0% liked)

Privacy Guides

16263 readers

1 users here now

In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.

This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.

You can subscribe to this community from any Kbin or Lemmy instance:

Learn more...

Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!

Want to get involved? The website is open-source on GitHub, and your help would be appreciated!

This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.

Moderation Rules:

We prefer posting about open-source software whenever possible.
This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
No soliciting engagement: Don't ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don't repost topics which have already been covered here.
News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
No misinformation: Extraordinary claims must be matched with evidence.
Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

founded 1 year ago

MODERATORS

jonah@lemmy.jonaharagon.net