I’m glad that they chose the AGPL when open-sourcing their server. I don’t see that many companies, especially ones offering a “product”, open-sourcing their work with a copyleft license.
Why should I use this over Immich?
Looks like it’s not really designed to be self hosted yet. So, if you’re self hosting, Immich is still probably the way.
Almost impossible to google for german users.
For now it seems like you need to modify and build the apps yourself to be able to use the newly open sourced backend server. This doesn’t make it very realistic to use for self-hosters.
If they ever change that, it might be worth another look.
If they’re nice enough to use the AGPL, I have some faith that they’ll also improve it for self-hosting.
What’s the benefit of this over shotwell?
Why does it need to be encrypted if it never leaves my device? I dont get it
It does leave your device, it’s connecting to either self hosted server or paid service cloud
I’m looking a for photo-storage option for the long-run.
Open-source is not a must, but nice. E2E encryption is not a must, but nice.
I just want to place to store, edit(?), categorize, search, share my photos. And I don’t want to the place to be Google, Apple, or Microsoft. So, this does look interesting.
However, I also want to low-maintenance, low-cost, stable long-term solution. I value convenience.
What options should I consider?
I’m looking a for photo-storage option for the long-run.
Open-source is not a must
If you’re looking for anything “for the long run” then open source should be a must, because everything else will eventually become unsupported and without source code access you’d have no recourse to continue maintaining it.
Proton Drive just added photo backup to their app. It’s new, and lacking features, but automatic backups and sharing are working.
The whole proton suite is pretty good, I’ve been very pleased.
Immich is a perfect photos app, and although still under heavy development it is quite polished already.
Low maintenance depends on your definition ai suppose. As it’s under heavy development you do need to often change the config with a new update.
But it has a Google Photos like interface, facial recognition and object/scene recognition and searchability (all of this is done locally on the server), etc.
What would be the best way to set it up on a raspberry pi, keeping in mind privacy & security?
Run the docker container rootless, password protect it, and don’t expose it to the Internet? Pretty much applies to any Docker container.
It’s a paid service with free trial.
The amount of marketing on their pages is triggering my sus radar a bit.
Some kind of marketing is better than having some or no documentation what it even does.
To be fair though, calling an open-source project “product” is really weird and gives away how they see it. As long as it’s free and the code is all there, the worst thing would be that the users have to migrate to a fork.It is a paid service.
I’ll give it a spinNevermind, this isn’t self hosted. There is no way i upload all my pictures to anyone else, encrypted or not.
If anyone cares about a self-hosted solution: https://github.com/LibrePhotos/librephotos
It was a paid service and it still is a paid service. However, now that they open-sourced the server, you can self-host.
What are you talking about?
