3 ms·
That's not it though - you can still write a file right next to the UserDefaults plist with anything you want without having to declare anything.
by akmarinov 3y ago
That's not it though - you can still write a file right next to the UserDefaults plist with anything you want without having to declare anything.
- mynameisvlad 3y agoJust because you can still do potentially malicious things through other means does not change the reasoning, intent or need for the UserDefaults change. If you want to write data without providing a reason, then go do that. Until Apple requires reasons for file writes. It’s literally a 2 second process, and it’s meant to provide transparency into what the developer is doing. That seems entirely beneficial to users. Sorry that being honest and taking a few seconds of your time is such a heavy burden.
- lapcat 3y ago> It’s literally a 2 second process, and it’s meant to provide transparency into what the developer is doing. What transparency? Almost every app in the App Store uses UserDefaults, and the only allowed reason to use it is, literally, "CA92.1". How is that transparency? > That seems entirely beneficial to users. How, exactly? > Sorry that being honest and taking a few seconds of your time is such a heavy burden. The dishonest developers will give the exact same "reason" as the honest developers. It's security theater.