I’d still like a deeper dive into how database corruption led to data restoration
It seems like deleting a photo must just be removing the entry from the SQLite database, and not actually deleting the photo?
this post was submitted on 24 May 2024
68 points (97.2% liked)
Apple
17445 readers
44 users here now
Welcome
to the largest Apple community on Lemmy. This is the place where we talk about everything Apple, from iOS to the exciting upcoming Apple Vision Pro. Feel free to join the discussion!
Rules:
- No NSFW Content
- No Hate Speech or Personal Attacks
- No Ads / Spamming
Self promotion is only allowed in the pinned monthly thread
Communities of Interest:
Apple Hardware
Apple TV
Apple Watch
iPad
iPhone
Mac
Vintage Apple
Apple Software
iOS
iPadOS
macOS
tvOS
watchOS
Shortcuts
Xcode
Community banner courtesy of u/Antsomnia.
founded 1 year ago
MODERATORS
Media library apps have been doing this kind of stuff forever. An index of the files + metadata allows for a better and more performant experience. But, if an entry in the DB gets pooched, file remains on the drive and is hidden from the user.
Many media library apps actually have a way to repair and or rebuild the library DB if it gets out of sync or corrupted. iTunes straight up put that feature in the menu bar. The Photos app will do it if you launch the app while holding command-option.
Back when iPods were king, how many of us had old music come back to life after a fucked up iTunes library was rebuilt? It’s kind of a similar issue.
Sure, an index makes sense for quick search, but I’m confused why deleting it wouldn’t remove it from the filesystem too
Is that why iPhones seem to have no idea how much disk space they’re using?
Given the rarity of this, it could’ve just been the normal random stuff that happens in computer land. Requests that don’t complete because they were interrupted by a crash, the rare bad block, etc. Or maybe it was just a bug that occasionally reared its head under certain circumstances.
Whatever it was, it wasn’t the first time a piece of software had an index that was messed up and out of sync with the stored files.
As for the iPhone storage thing you mentioned, I don’t know what you’re talking about. There was a IOS 17 bug early on where people mentioned that the OS needed a restart to claw back space from temporary install files and caches.
That said, the corrupted DB we’re talking about appears specific to the photos app. It’s not the file system index. It’s basically a glorified preference file.
E.g. iCloud says it’s using 13.4 GiB to store photos, Settings -> General -> iPhone Storage says I can save 15.5 GiB because they’re backed up on iCloud, and if I use idevicebackup2 to pull everything off the phone, there are 21.7 gigs of photos
I’m wondering if these discrepancies are related to the photo app not actually deleting pictures from the filesystem
Weird. I’d bet money on syncing issues, compression, etc. But who knows, if you have a Mac you can rebuild the library, let that sync, and see what happens.
https://support.apple.com/guide/photos/repair-the-library-pht6be18f93/mac
I’d disregarded compression as a possibility because the wording is “full resolution photos and videos are safely stored in iCloud”
There is lossless compression. Not saying that’s the cause of the varied number, but it is a common thing.
They’re already using HEIC/HEIF
I would be disappointed if they’re compressing it even more on iCloud. You can’t generally meaningfully compress a compressed file
That’s not how lossless compression works. No data is lost.
For example, if you zip a folder of images, then unzip them, the pictures come out with their original sizes and structure. Zip is lossless.
Let’s use the analogy of a dish sponge.
Let’s pretend you wanted to make a dish sponge smaller. Lossy compression would make the sponge smaller by cutting off parts and throwing them away. Lossless would make it smaller by squish the sponge, and it would return to its normal shape once you stopped squishing it.
For your analogy, you can’t put more water in a sponge that is completely saturated
Trying to compress a compressed file doesn’t really work - at least not for a meaningful gain in storage size with zip, bzip, 7zip, gzip, xz, lzma…
In a now-deleted post, a Reddit user last week alleged that their photos…
A recently deceased Boeing employee alleged that the quality control process…
In a now-deleted post, a Reddit user last week alleged that their photos reappeared on an iPad they sold to a friend, despite them having erased the content of that iPad prior to selling it. Apple tells me that this claim was false.
I had a feeling this was the case. It makes absolute zero sense that a fully erased device on a different Apple ID could have this issue.
It was such an obvious troll. Nobody with the slightest knowledge of how iOS works bought it. Just click bait.
This is weird especially because iOS uses file based encryption, and when resetting the device the key is thrown away. So even if the files were still there, they would not be readable. I think they didn't reset the device properly and instead deleted the apps manually is likely why this happened
Lemmy: Apple doesn’t care about your privacy and is secretly keeping your deleted photos because they want your data.
Reality: 1) iCloud photos are E2EE 2) Apple doesn’t have an encryption backdoor, which is why the feds keep pushing for one 3) violating deletion requests is illegal in their core markets
Aaaand… 4) your ass probably already has thousands of photos that you didn’t delete. They don’t need your deleted photos if they want to train models. They have more than enough stuff that you didn’t delete.
Well people had other people's photos popping up in their own photos app. So not sure how they handle 'encryption'. But it's best to treat all photos uploaded to cloud as public, because that's likely how it is. Can't trust Google, Amazon or Apple with your data when they can and are making so much money off of it.
No one was able to reproduce that. That claim of seeing others photos was from a Reddit user who deleted the post.
Small correction - iCloud Photos are only end-to-end encrypted if you enable Advanced Data Protection, which was introduced in December 2022, and otherwise Apple has the keys. See https://support.apple.com/en-us/102651 for more details.
So the uploaded photos in question couldn’t have been e2ee. Even so, it’s reasonable for people to question the legitimacy of e2ee given instances where it’s been shown to be a lie or for the data to also have been transmitted without e2ee, like Anker’s Eufy cameras’ “e2ee” feeds clearly being accessible without keys from the user devices, or WhatsApp exposing tons of messaging metadata to Meta.
That said, I personally wasn’t using iCloud Photos prior to enabling Advanced Data Protection, and I had a few deleted photos show up from several years ago, so Apple’s explanation makes sense to me. And, like you’ve pointed out, most of the speculation was devoid of any critical thinking.
As its all proprietary you can’t, and basically nobody can, say anything about a backdoor. It’s pure trust in this corporation.
It’s not proprietary. It’s the AES 256 standard.
iCloud is proprietary by definition because Apple has not publicly released its source code under a free license.
But AES is
AES is a specification, not a piece of software. Closed-source software like iCloud that implements the AES specification is still proprietary.
Yes. I’m referring to the encryption standard and I’m saying the photos stored in the cloud service are E2EE.
The OS is, it runs everything and can do anything locally.
People were claiming Apple was secretly keeping deleted photos in the cloud. Which was what my parent comment was about.
Apple fixes bug: wHy dOeSn't aPpLe eLaBoRaTe wHaT ThIs bUg wAs aBoUt
Apple elaborates: WhO Is gOnNa bElIeVe aPpLe