348
Ente - Open sourcing our server
(ente.io)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 01 Mar 2024
348 points (97.8% liked)
Selfhosted
37771 readers
429 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Their model is that the server doesn't know what the pictures are.
Which is fine. It's cool that it exists as an option, especially with someone else hosting your pictures. But it's not for me. I want my server to see my pictures so it can play with them.
Papa jpeg: "this little jpeg went to market, this one stayed home, and this one went weeeeeee all the way along the download stream!"
Other little jpegs: "hoorayyyyyyy"
lol I want some of them served publicly. And at some point I want to do other processing of the contents of photos.
I have absolutely no opposition to the existence of an end to end encrypted photo service. If the process of adding new devices is easy enough, it's what I'd want from someone else hosting. But it's not what I need for personal hosting.
Which, again, is fine. There's absolutely a place for it. But the dude we're responding to is acting like not doing it is a liability when there's very good reason not to. (I think it's because of platforms trying to muddy the water of what end to end encryption means to pretend they do it and confusing him.)