I would add file types to the list. JPEG is easy to rotate, but what about other image filetypes, images with embedded video, different video file formats etc.
Comment on Where is Immich going to be in 1 year? What's your prediction?
8uurg@lemmy.world 18 hours agoAlso ImageTragick was a thing, there are definitely security implications to adding dependencies to implement a feature in this way (especially on a shared instance). The API at the very least needs to handle auth, so that your images and videos don’t get rotated by others.
Then you have UX, you may want to show to the user that things have rotated (otherwise button will be deemed non-functional, even if it uses this one-liner behind the scenes), but probably don’t want to transfer the entire video multiple times to show this (too slow, costs data).
Yeah, it is one thing to add a one liner, but another to make a well implemented feature.
cron@feddit.org 16 hours ago
rarsamx@lemmy.ca 11 hours ago
You can start with what you can. What can provide the most value and iteratively improve from there.
Sometimes as a developer or even product manager, you don’t know what feature complete really means until people start using it.
Oh, by the way: imagemagick.org/script/formats.php
rarsamx@lemmy.ca 11 hours ago
Once you implement Authentication/Authorization it’s fairly simple to add a new function.
I think here, the problem is not the complexity of the task, but the developer’s prioritization based on all the backlogged features.
Still, users can do this on their own. Directly on the folder, autorotating all pictures using wildcards.