101–110 of 124 posts
Earlier quoted context omitted.
The Ente self-hosting proposition seems strange. Why would I want to e2e encrypt my photos that I self-host? Sounds like it will only make life more difficult.
You may want to self-host for your family or close friends while guaranteeing them privacy.
Earlier quoted context omitted.
The Ente self-hosting proposition seems strange. Why would I want to e2e encrypt my photos that I self-host? Sounds like it will only make life more difficult.
Because you want to access your photos remotely, or give access to more people to certain albums. If the point is to just store them locally and no remote access is needed, a hard drive would probably be enough.
Earlier quoted context omitted.
The Ente self-hosting proposition seems strange. Why would I want to e2e encrypt my photos that I self-host? Sounds like it will only make life more difficult.
1. "Self-hosted" doesn't always mean "on your own hardware." Some people rent VPSes. This helps keep their data safe. 2. The software is provided without modification; I think it would be stranger to remove the encryption.
Earlier quoted context omitted.
Been running immich on my home server for about a year now. Near zero maintenance stack, incredibly easy to update, the client mobile apps even notify you (unobtrusively) when your server has an update available. The UI is just so polished & features so stable it's hard to believe it's open source.
This seems in stark contrast to others complaining enough about breaking updates that I haven't bothered to try it until it is deemed "stable". Is it really that stable and flawless in terms of updates? Because I'm sat here with ZFS, snapshotting and replication configured and wondering why people scare others off of it when the tools to mitigate issues are all free and should be used anyway as part of a bog-standard…
I also perform all my updates manually - it's fully automated: a simple script that runs in seconds across my entire home server - but I don't have it on any schedule so I'm not doing anything blind. That at least affords me the luxury of being present if/when anything breaks (though for Immich that has not occurred yet).
Earlier quoted context omitted.
I wanted to like Photoprism because unlike Ente and Immich, it supports SQLite databases and doesn't require postgres (I want to keep home lab maintenance to a minimum) but the UI was difficult to like and I couldn't get hardware encoding working on my Intel N100 GPU.
What about Postgres isn't low-maintenance? The ball-ache of SQLite not scaling outweighs any "maintenance" Postgres needs (it really is just set-and-forget and use a Docker container to schedule database backups—whole thing takes a couple minutes).
Also considering the type of workload, I imagine photo albums to be write heavy upon photo imports but read heavy afterwards which sqlite should excel at. I'll mostly be syncing pictures from our phones, and it'll be me and the wife using it. Postgres is overkill for my needs.
What about having to do db migrations across major updates?
Earlier quoted context omitted.
I wanted to like Photoprism because unlike Ente and Immich, it supports SQLite databases and doesn't require postgres (I want to keep home lab maintenance to a minimum) but the UI was difficult to like and I couldn't get hardware encoding working on my Intel N100 GPU.
What about Postgres isn't low-maintenance? The ball-ache of SQLite not scaling outweighs any "maintenance" Postgres needs (it really is just set-and-forget and use a Docker container to schedule database backups—whole thing takes a couple minutes).
I think Immich checks a lot of these https://immich.app/
Earlier quoted context omitted.
If there's a server involved, there's no reason not to have sensitive files and information end-to-end encrypted, whether self-hosting or not.
You do want to have things encrypted in transit and at rest. e2ee means server admins (I) cannot access the user's (mine) photos.
edit: To explain further why it's almost always desirable:
You guarantee that you and your users' information is safe if the server is compromised, if an admin goes rogue, or if local bodies of power request their information from you.
The information can't be sent to third-parties by design.
Any operations / transformations that need to be applied to the information will have to either be done via homomorphic encryption or on the client-side (which is much more likely to be open source / easy-to-deobfuscate compared to blackbox server code).
Earlier quoted context omitted.
You do want to have things encrypted in transit and at rest. e2ee means server admins (I) cannot access the user's (mine) photos.
The server admin can still access their own photos via the client. They wouldn't be able to access the photos of other users. edit: To explain further why it's almost always desirable: You guarantee that you and your users' information is safe if the server is compromised, if an admin goes rogue, or if local bodies of power request their information from you. The information can't be sent to third-parties by design.…
E. g., “Any operations / transformations” includes facial recognition, CLIP embeddings, &c; you want to run this on the server, overnight, and to be able to re-run at a later date when new models become available. Under e2ee, that’s a round-trip through a client device at every model update. So that’s a significant downside, for no important upsides in the case when you and your family are the only users.
Earlier quoted context omitted.
The server admin can still access their own photos via the client. They wouldn't be able to access the photos of other users. edit: To explain further why it's almost always desirable: You guarantee that you and your users' information is safe if the server is compromised, if an admin goes rogue, or if local bodies of power request their information from you. The information can't be sent to third-parties by design.…
I understand what e2ee is, thank you. I just don't think it’s justified for self-hosted photo servers . E. g., “Any operations / transformations” includes facial recognition, CLIP embeddings, &c; you want to run this on the server, overnight, and to be able to re-run at a later date when new models become available. Under e2ee, that’s a round-trip through a client device at every model update. So that’s a significant…