- cross-posted to:
- foss@beehaw.org
- lealternative@feddit.it
- cross-posted to:
- foss@beehaw.org
- lealternative@feddit.it
cross-posted from: https://lemmy.ml/post/12624334
Ente - Open sourcing our server
cross-posted from: https://lemmy.ml/post/12624334
Ente - Open sourcing our server
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.)