3 ms·

It’s be mentioned elsewhere and I’ll mention it here again. UserDefaults does not belong on this list. Effectively every app on the store uses it in some fa

by ecf 3y ago

It’s be mentioned elsewhere and I’ll mention it here again. *UserDefaults does not belong on this list.* Effectively every app on the store uses it in some fashion. Apple, please. Remove this.

matt-attack 3y ago
Can you explain what this API is for and how it’s presumably abused?
- graypegg 3y ago
  https://developer.apple.com/documentation/foundation/userdefaults https://developer.apple.com/documentation/foundation/userdef... It appears to be the permission allowing access to this API. Based on the description, it sounds like this is how you access the user’s preferences (preferred measurement units, default playback speed, etc) Maybe it could be used for fingerprinting users? But also, this seems pretty innocuous to me.
- ecf 3y ago
  It’s iOS’s API for managing key-value user settings. User wants kilometers instead of miles? Store the selection in UserDefaults. They want larger font size? Store it in UserDefaults. Different accent color? You guessed it, also UserDefaults. Apple wanting justification for an app having settings (which is pretty much every app on the planet) is ridiculous.
  - sigilis 3y ago
    In the developer documentation it mentions that the restricted activities involving UserDefaults involve writing data that other apps can read, or reading other app's data in UserDefaults. It seems odd to me that if this is a security or privacy issue it couldn't be addressed by a technical means, like preventing UserDefaults from reading from other app's data at all, rather than having every developer that wants to store preference data pinky promise that they won't performed the proscribed actions. I'm not looking forward to any increase in the amount of nonsense I must deal with to develop for iOS. They seem to have a some kind of garbage boilerplate lower limit that they feel giving us macros and SwiftData has put in danger.

It’s be mentioned elsewhere and I’ll mention it here again. *UserDefaults does not belong on this list.* Effectively every app on the store uses it in some fa

by ecf 3y ago

It’s be mentioned elsewhere and I’ll mention it here again. *UserDefaults does not belong on this list.* Effectively every app on the store uses it in some fashion. Apple, please. Remove this.

matt-attack 3y ago

Can you explain what this API is for and how it’s presumably abused?

graypegg 3y ago
https://developer.apple.com/documentation/foundation/userdefaults https://developer.apple.com/documentation/foundation/userdef... It appears to be the permission allowing access to this API. Based on the description, it sounds like this is how you access the user’s preferences (preferred measurement units, default playback speed, etc) Maybe it could be used for fingerprinting users? But also, this seems pretty innocuous to me.
ecf 3y ago
It’s iOS’s API for managing key-value user settings. User wants kilometers instead of miles? Store the selection in UserDefaults. They want larger font size? Store it in UserDefaults. Different accent color? You guessed it, also UserDefaults. Apple wanting justification for an app having settings (which is pretty much every app on the planet) is ridiculous.
- sigilis 3y ago
  In the developer documentation it mentions that the restricted activities involving UserDefaults involve writing data that other apps can read, or reading other app's data in UserDefaults. It seems odd to me that if this is a security or privacy issue it couldn't be addressed by a technical means, like preventing UserDefaults from reading from other app's data at all, rather than having every developer that wants to store preference data pinky promise that they won't performed the proscribed actions. I'm not looking forward to any increase in the amount of nonsense I must deal with to develop for iOS. They seem to have a some kind of garbage boilerplate lower limit that they feel giving us macros and SwiftData has put in danger.