This is a text automatically translated from Italian. If you appreciate our work and if you like reading it in your language, consider a donation to allow us to continue doing it and improving it.
Content index
It is possible that you have read around the photo backup problem on iOS 17.5, some people have in fact complained about having found some photographs in the gallery that they had certainly deleted many years before 1. Ente Photos he didn't miss an opportunity and published a post on his blog to publicize the fact that they actually delete photographs.
Apple seems to have confirmed the problem and has too released version 17.5.1 that he should fix this problem without commenting or giving any real explanation as to what happened.
This update includes important bug fixes and fixes a rare bug where photos with database corruption could reappear in your Photos library even if they were deleted.
iOS 17.5.1
In “Apple communities”, such as the 9t5Mac blog, we try to minimize what happened as much as possible but on balance what happened is very serious and disturbing whatever the reason.
•How Ente Photos Deletes Photos (Better than Apple)
Ente Photos saw fit to publish a post trying to turn the news in their favor. The thing we particularly liked about this post it's the fact that they published the process by which this deletion occurs by identifying it on GitHub. Yes because Ente Photos, unlike Apple products, is completely Open source and if it says to delete deleted photographs can prove it with the source code published and verifiable.
And since a source code of thousands of lines is not really within everyone's reach to process, they also did something very interesting that is not often seen. They highlighted the various processes by which this occurs. In this way even those who understand little about programming can at least understand what is happening.
Here are the processes on GitHub
Ente Photos identifies three ways to delete your files:
- Delete a file
- An album
- By deleting your account
We are therefore told that as soon as you delete a file this it is immediately put in the trash and is recoverable within 30 days. Then they will leave two tails which will allow its cancellation.
What is important to note here is, when we process a file for deletion, we also remove all metadata related to that file – including the object keys (path) to access its blobs and the necessary metadata to help our clients decrypt them. So once a deletion request is processed, the file will become inaccessible to Ente, and to you.
How Ente deletes data
Even when you delete an album the process is similar e.g it is also identified here via the code on GitHub.
A similar thing happens when you delete your account.
If you are interested in learning more you can read their blog post.
•How Ente Photos Deletes Photos (Better than Apple)
Ente's approach is always very open, recently they even allowed the Self-Hosting of your application also publishing the source code of the server on which it runs.
Ente Photos, we remember it, it is one of the best alternatives to Google Photos and at this point we would also say that it is one of the best alternatives to Apple iCloud.
We often talk about it because, as you may already know, it is one of our favorite alternatives and so far it has always lived up to expectations.
If you think this could be a good opportunity to try it, we remind you that there is no completely free version but you can try it with 5GB free for a year.
Also, the discount with the code should still be active LEALTERNATIVE which should allow you to get the 10% discount for the first year. We always remember that we do not take commissions for these discounts but ask for them exclusively for those who read us without having anything in return.
If you are interested you can also find our review.
•This tag @loyal alternatives is used to automatically send this post to Feddit and allow anyone on the fediverse to comment on it.
Join communities
If you have found errors in the article you can report them by clicking here, Thank you!