- write access
- read access (all photos)
- read access (through a special iOS picker that acts as a middle man)
The longer people have their phones, the more photos they have. And with them a whole lot of meta data such as location etc.
I simply don’t trust most apps these days that they really don’t touch any of that data.
Of course, you can already "share" a photo with an app, but this doesn’t let you change a profile picture in Instagram for example.
The cynical person might say: why not stop using these apps in the first place? Because it’s difficult to say who is exploiting photo library access and who is not. Does VSCO do it? I’d think they have no interest, but it’s too much based on trust vs. something I can control.
Stripping location metadata before handing photos off to apps would be nice too.
Where Android/Google itself is a bigger problem perhaps than the 3rd party apps.
Its constant presence is an artifact of apple pretending the mouse will only be used by those who need the pointer always for accessibility reasons.
As I said above the only real criticism I have is that the pointer/accessibility box doesn't disappear when the mouse is disconnected.
I haven't tried it over Remote Desktop (I don't know if the "raw" mouse presses are relayed), only to interact with native iOS Apps.
Admittedly, the distribution of Android devices on 8.x+ is higher than I even expected before looking at this.
[0] https://developer.android.com/guide/topics/connectivity/wifi...
[1] https://developer.android.com/about/versions/pie/android-9.0...
https://developer.android.com/about/versions/marshmallow/and...
By eye, that covers nearly 75% of current devices.
How on earth it occurred to someone in the first place, that determining whether the phone is in use or not and reading the phone #, IMEI, etc. should be the same permission is beyond me.
Also Apple (as opposed to Google) is the one actively cooperating with Chinese government and giving them decryption keys for iCloud.
If you look beyond the marketing spiel it's kinda ridiculous marking one of those corporations to be more trustworthy than the other.
Sorry, what?
2.) Apple admits it was giving Siri recordings to contractors with no ability to opt out of the functionality. This included false activations not meant for Siri. Seemingly what happened near iPhones did not stay on iPhones:
https://www.theverge.com/2019/8/23/20830120/apple-contractor... [August 29th]
3.) In 2016 Apple shifted their iCloud servers to China to abide Chinese limitations and give access to content on governmental request. It seems, again, what happens on iPhone does not stay on iPhones: https://www.latimes.com/business/technology/la-fi-apple-chin...
But of course, this whole topic on HN shows that the money on marketing is well spent. Lesson for Google and Facebook: up the marketing spending to keep repeating how privacy concious they are. ;)
iOS 13 has several great privacy-focused changes:
- WiFi SSID is protected behind location permissions (ie, an app must request and be granted location permissions to be able to access the current SSID)
- Bluetooth has additional permission prompts (as detailed in the article)
- When an app has been using location data, the user is periodically prompted to confirm continued background location use (with a map of locations the app has used).
- Safari has several on top of all these, like prompting a user to allow cross-site cookie loading, etc
In some of these, Apple is catching up to Android, and in others, it is ahead. Either way, it seems that most of these come from a directive from inside Apple to clean up 3rd party app behavior, likely prompted by things like last year's analytics & enterprise deployment scandals.