Yes, it is?
Your rant doesn’t make sense. Asking for suggestions because you’re not OK with being spied on (especially when you’re perfectly willing to absorb the hosting costs yourself or pay for a service that isn’t hostile) is perfectly valid behavior.
I could get the “default” to facilitate setup, but as far as I’m concerned it’s seriously fucked not to have the first step of your script be replacing it with the user’s own choices. It’s really hard for me to trust the security as a whole of a project that does that by default, especially because it’s intended to be for inexperienced users and there was no indication during the setup process or other included information that that was the case.
Serious question: last I looked at casaOS (because I liked the hardware), they had SSH open and accessible to default passwords by default. This scared me off hard.
Is this still a thing/are there other glaring security holes?
He wants all of his books in one index.
Discussing piracy is most definitely not illegal in the US. It’s protected by the first amendment, and there aren’t laws that even try to restrict it.
The only part of the DMCA that really has any complexity is the anti-circumvention bit, and that has no relevance anywhere to discussing piracy or tools that can be used for piracy.
He’s talking about user generated content from other users.
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.)
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.
Yep, documentation and a good base level default installation configuration/guide with minimal friction.
I’m perfectly willing to play around once I know at the basic level that the core flow is going to work for me. If it takes me digging through a stack of documentation (especially if it’s bad) to even get something to experiment with on my own system? I won’t bother.