cross-posted from: https://lemmy.ml/post/12624334
Ente - Open sourcing our server
I’m unsure about the end-to-end encryption aspect. While this feature is great for a cloud service like ente.io, it doesn’t really help much in a selfhosted scenario - and might make backups more complicated. Any other opinions on this?
Do you want your ISP to be able to spy on your private pictures when uploading them to your self-hosted server? End-to-end encryption is a no-brainer every time you transmit private data online
Would probably be trivial for a local authority to hack your server and collect the necessary info that way.
I mean that’s the main reason I self-host anyway.
We’ve consolidated all our code into a single repository – just clone ente-io/ente on GitHub, and you will have at your disposal a state of the art, end-to-end encrypted, full stack (mobile/web/desktop clients, the server, and a CLI to boot) alternative to Google Photos and Apple Photos.
This seems a disadvantage, a single repo that does everything seems inconvenient and unnecessarily complex for a casual hobbyist that wants to try the project
The flutter apps and the electron app are unrelated to the server+web.
Same for the separate 2fa app
If you want to contribute to something you need to fork everything.
Because this contains everything that is served by ente in their commercial offer in the way that’s suited in a professional way (photos stored in S3-like storage on minio server), not just photos, also future projects you might not want to run on your server like ente lock and ente legacy