Ente - Open sourcing our server
Ente - Open sourcing our server
ente.io
Open sourcing our server
cross-posted from: https://lemmy.ml/post/12624334
Ente - Open sourcing our server
56 comments
-
AGPL-3.0
Nice
-
I'm trying to learn about licensing. Why do you like AGPL-3.0 compared to others?
-
The AGPL applies copyleft to web services. If you're learning about licensing, it might be worth googling copyleft. Fascinating concept, and, in my opinion, something to subscribe to.
-
If you haven't already, check out https://choosealicense.com/licenses/ . This gives a broad overview of the common open source licenses. And if you're just starting out, one of the first things you'll want to learn is that the licenses fall into either a permissive or copyleft category. You'll want to make sure you understand the difference between those broad categories.
Shortly, permissive have less to no strings attached to use their code, and copyleft requires you to retain the same licensing terms meaning if you publish under GPLv3 then someone using/ modifying your code needs to also publish under GPLv3. Copyleft licenses ensure that open source code stays open source.
-
In very basic terms - GPL means that any modifications you make to a code base and distribute to public, you need to keep the license as GPL and open source all your modifications.
Once cloud started becoming a thing, the cloud vendors went "Well ackchyually🤓, the code changes we're making are hosted on OUR server so we're not technically distributing them to the public. So fuck you we have no obligation to make them open source".
Which is why AGPL exists so even server side code needs to be public. Since the application in question here is a backend service, it'll always be used server side and so any forks need to be open source.
-
-
as should be
-
Only really nice when not CLA is required and every contributor retains their copyright. Ente doesn't seem to require a CLA.
Otherwise it allows the owner to just take the changes from their contributors and change the license at a later date.
-
edit: the two issues i raised in this comment had both already been addressed.
this was the developer's reply on matrix:
- We do have a CLA: https://cla-assistant.io/ente-io/ente
- We will update the iOS app to offer you an option to point to your self hosted instance (so that you can save yourself the trouble of building it): https://github.com/ente-io/ente/discussions/504
- The portion of the document that deals with authentication has been outdated, my bad. We've adopted SRP to fix the concerns that were pointed out: https://ente.io/blog/ente-adopts-secure-remote-passwords/
-
Ente doesn’t seem to require a CLA.
It turns out, they do have a CLA (with full copyright assignment 😢).
-
-
-
How does ente photos compare to immich?
-
I love immich, but I'm going to settle for something that doesn't require to modify the compose every couple of months due to breaking changes. Trying to apply changes for two breaking updates in one go killed it for me.
I'll check this one for the time being
-
If you haven’t already ruled it out, I recommend checking out Photoprism. It was the first app I ever self-hosted using Docker and I haven’t needed to change my config because of breaking changes yet.
-
I understand this, but that way you always read the update notes and you control what version you install. This can be a good practice.
That stuff breaks is not so nice though.
-
The 1.95 update was trivially easy to update with their instructions if you already have the skill to use docker compose.
-
-
Was about to ask the same
-
-
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
-
-
If you really want to serve the self-hosting community, please improve your documentation. As someone unfamiliar with this product, I have no idea what to do with this once I clone the repo. I hunted and found a compose.yaml file, but it's not clear if this is all I need.
-
The docs directory literally has a stub on getting the repo up and serving and also a note that they are cleaning up and working on the documentation https://github.com/ente-io/ente/tree/main/docs
-
-
Happy to see some alternatives, but I’m a very happy user of PhotoPrism (+PhotoSync) so will stay there for now. Agreed that encrypted at rest isn’t all that helpful for a self-hoster.
-
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?
-
Not only backups, but also migration
-
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
-
-
Happy to be a paying customer of Ente, always delivering 🙌
-
So would this be a good alternative to Synology photos?
-
@ioslife good competitor to google photos?
-
The first two things I saw:
- docker seems to be required
- the download page seems to require javascript
Too much neu hype. Done.
56 comments