[dead]
Immich 3.0
231–240 of 313 posts
Re: Immich 3.0
#232Great app! Great to see the progress with it.
The biggest complaint has always been how hard it is to self-host it, but that's not true anymore. If you have a good underlying system that handles all the boring stuff, you can actually have a pretty good experience.
I'm biased because I'm building an OS for this, and it makes spinning up imich so easy.
Re: Immich 3.0
#233My only disappointment with this release is that the beta version of workflows does not have the ability to sort photos into albums by face detected (yet). That’s what I’ve been waiting for as both Google Photos and Ente support smart albums
Re: Immich 3.0
#234Has anyone personally upgraded to 3.0? How is the experience?
docker compose down
IMMICH_VERSION=v3
docker compose pull
docker compose up
No issues so far. The web UI is not significantly changed, the biggest improvements are on mobile.
Re: Immich 3.0
#235There's a lot of things I spent a ton of time setting up, use once, and then never again. Tons of things that are easy to set up, and provide small benefits every day for a long time. Immich has got to be the thing that I've spent ages setting up, use extremely infrequently but the one time a year I use it I'm so happy I did. Great software.
In my case I spent it not so much time setting it up, some time upgrading with some manual work required from time to time with breaking changes (but not so often) and I use it weekly, it just works and it's wonderful.
Re: Immich 3.0
#236I have come to the realisation that I don't need 10,000 photos. I probably need Which I am yet to do...
Print them, absolutely, you won't regret it! But it's also good to keep a local and locally owned digital version neatly organized.
Re: Immich 3.0
#237Immich is such a no-brainer replacement for Apple Photos or Google Photos, combined with VPN like Tailscale, it's almost a drop in replacement
I’ve been using photoprism. Should I switch?
I'm in the same boat, and have been meaning to try immich but slightly worried about migration effort. Should I import fresh into Immich or setup my existing photoprism as an external library? I think the former is probably correct, but the latter might be easier?
Anyone have experience with this? I haven't done much modification or album creation in photoprism, so am happy to start from scratch on that front.
Re: Immich 3.0
#238Earlier quoted context omitted.
I really don't think you want E2EE for this. I host storage for family and friends, I haven't set Immich up yet (don't think I'd have space for everyone's photos) but the choice is between: 1. "Hey just so you know, I have access to everything you upload here". 2. "Do NOT lose your password or your data will be GONE FOREVER and I CANNOT get it back". I definitely prefer 1 and I'm sure my users do too. They shouldn't…
I do agree that this is a use-case. Now a use-case for E2EE is if you want to host it on a VPS, I would say. I wouldn't trust the VPS with the photos of my friends/family.
You can run it on an encrypted volume on a VPS. Technically, it is also possible to use confidential VMs, but I have not at all kept up with those developments these days. Confidential here means that the SoC/CPU provides the ability for VMs memory to be encrypted with a key that the host never has access to. There's also remote attestation for it. I personally like e2e encryption at the application layer in some applications, but I personally do not think that it'd be practical for immich unless they also do confidential compute for the classifiers and identifiers. That is something Apple can do because they have the capital, not an open source project.
Re: Immich 3.0
#239I teach a free software development course to my undergrad students. It's really exciting to stumble upon one of the work they did for my class in the wild (it's the first listed bug fix — which is the last of the three pull requests this student got merged in Immich during my course). I feel so proud! :)
Naww, that's awesome! gj :)
Re: Immich 3.0
#240Earlier quoted context omitted.
> How do techies and devs of all people not understand I find it interesting to start with this, and follow with: > There is no reason why E2EE services can't provide recovery or emergency access mechanisms If the service can help you recover your data after you lose the key, it means that they have the key, and therefore it's not end-to-end encrypted. That's the whole point of E2EE.
> That's the whole point of E2EE. No it's not. The point of E2EE is that only the client apps decrypt/encrypt content, and the server just processes the encrypted bits. Most E2EE service providers do this by encrypting your encryption key. That's how you can login on other devices without you having to store and import an encryption key every time. When you login they send you an encrypted blob that contains your enc…
In a recovery scenario, you don't have the password or whatever you used to encrypt the key.
And again: the whole point E2EE is that you don't have to trust the provider. Open source in general doesn't help you here because you don't know what software or which version of the code the provider is running. Your only chance is to run open source client software, review it to ensure E2EE has been implement properly, then you don't need to trust the provider.
Either the provider knows the secret, then they can help you in a recovery scenario, but then they also can read your data. Or they don't know the secret, in which case they cannot help you in a recovery scenario.