Hacker Newsnew | past | comments | ask | show | jobs | submit | geekologist's commentslogin

That reads as rewarding them for taking your account hostage


immich is an extremely polished, FOSS alternative to google/apple photos. It's an investment, but a 4 bay NAS running immich should do nicely. Additionally I backup snapshots to Backblaze B2 via restic which runs another $5/TB


For me personally Immich is a non-starter because its not end-to-end encrypted.


It runs on your own hardware. There is nobody else who has access to unencrypted data.


Storage vps are cheap. Why would I have to run it in my own house?

:)


Why would you need it to be end to end encrypted anyway? You’re running it. Set it to only upload photos when you’re on your home network and you’re fine. Or fork it and make a PR and make it e2e encrypted.


You can’t just “fork it and make a PR and make it e2e encrypted”. All the features run serverside, e2ee is fundamentally impossible because of its design, of which you seem to know fuck all.

I’m being dismissed by I run a rather large homelab and I still want my photos iCloud like, where end devices decrypt and run ML. Immich is a Google Photos clone where you give it everything and some server does all the magic.


Hm, you can just run it on an encrypted volume. And put an ngnix in front of it to handle https. There you go end to end encrypted.


What are you talking about. It’s literally open source. Here’s the server code https://github.com/immich-app/immich/tree/main/server You run the server. You can make the entire thing e2e encrypted if you want.

You could even set it up so that it could only backup over tailscale or wireguard through a tunneled connection so ALL of your traffic is e2e.


You have to disable Cloudflare proxy which is not an option with tunnels. It's technically against TOS to proxy non-HTML media anyway. I just ended up exposing my public IP.


> I just ended up exposing my public IP.

I considered doing that too. My main problem with it is privacy. Let's say I set up some sort of dynamic DNS to point foo.bar.example.org to my home IP. Then, after some family event, I share an album link (https://foo.bar.example.org/share/long-base64-string) with friends and family. The album link gets shared on, and ends up on the public internet. Once somebody figures out foo.bar.example.org points to my home IP, they can look up my home IP at all times.


It's another cost but running a reverse proxy from a VPS would solve this right?


Don't know how far along your career you are, but as a youngin', the occasional thought piece like this that introduces interesting new ideas and challenges me to reevaluate how I approach things have proven to be quite formative in retrospect


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: