Rosyna

The problem with not having a probationary period for 15% cuts is developers will move to subscriptions en masse because 85% is far more than 70%.

And no one wins if every single app/game developer moves to subscriptions. It only ends up screwing all users and those developers that choose not to go to the subscription route.

The probationary period Apple added was to discourage developers from being jerkasses and moving to subscriptions without having the services/content to offer.

gatorguy said:

Rosyna said:

The fix would be for WhatsApp to either move to encrypted CoreData (as the article suggests) or, more simply, to just use the SQLite VACUUM command (https://www.sqlite.org/lang_vacuum.html) on the app tombstoning notification (https://developer.apple.com/library/ios/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/StrategiesforHandlingAppStateTransitions/StrategiesforHandlingAppStateTransitions.html#//apple_ref/doc/uid/TP40007072-CH8-SW24) if any chats had been deleted.

The latter fix is more likely to occur with WhatsApp because it's almost trivial to adopt.

Not specifically mentioned in AI's article:
"
Apple’s iMessage has this problem and it’s just as bad, if not worse. Your SMS.db is stored in an iCloud backup, but copies of it also exist on your iPad, your desktop, and anywhere else you receive iMessages. Deleted content also suffers the same fate."

Because Apple never says anything about being able to securely delete text messages.

It's especially moot when you can get them from the carrier and there is no way to guarantee what happens on the other side (the person that sent it or received it) is doing with the text message.

It is neither "just as bad" nor "worst".

I guess it's important to note that only about 25% of the content in any one of Zdziarski's post is technically accurate. The rest is either FUD, wild guessing, or just paranoid weirdness for PR purposes. His unfounded paranoia has resulted in some very useful, very secure Xcode features getting removed because of the bad PR it generated for Apple, even though his claims were incorrect.

tallest skil said:

AppleInsider said:

Earlier this month media outlets latched onto a blog post from freelance composer James Pinkstone, who claimed iTunes deleted some 122GB of music from his laptop, including original works. After speaking with Apple support representatives, Pinkstone came to the conclusion that the mishap had roots in the way Apple Music and iTunes handles music files.

Specifically, Pinkstone believes Apple Music scanned his iTunes library, matched those tracks with streaming copies -- or uploaded originals -- then automatically removed the local files. 

And people wonder why I’m skeptical of the “cloud-only” future that so many companies want to push.

Except that iTunes can't do that and doesn't do that.