I set this container up yesterday. Technically it’s running. But all the settings are in the fucking sql db, and I know fuck all about sql other than drop tables is funny meme from xkcd. But also, ignoring the settings, I would like to point out that there is effectively no client. I mean, there are two official ones - the depreciated one, and the alpha one, and the alpha one has a total of 4 releases with the newest being two years ago. How do you deprecate a client when the server is still in alpha? What the fuck? And on all pages it screams ‘this is alpha testing software, do not use as a daily’. Also the docs are, uhh… rough. If rough was falling 4 stories into a bed of poisonous cacti. It took me 3 hours to get the container running properly and finally poking at the db. It’s as organized as my bedroom (‘it’s somewhere in this dresser, I think…’).
The idea, the potential, is brilliant. Literally everything about getting it working though…
So you’re offering to manage my ~40 services, and make sure that all the dependencies are met - and none conflict…?
I mean, I enjoy hosting things myself, but I’m not going to invite issues that have been resolved by simple solutions. I’ve been around the block with dependency hell, fuck all of that. Now if I was getting paid like 6 figures instead of zero, sure boss, whatever the fuck you say boss, job security all day long. But unless you’re offering, I’m sticking with the easy way.
I mean, that’s true regardless of how it is running. If the service is externally available, it will be probed for vulnerabilities. At least with a container, you can ward off what files it has access to, so an attacker can’t just ransomware your entire NAS with a single vulnerable service.
And thaaaat’s why it’s head/tailscale or nothing for me. I’m smart enough to know I don’t know enough to be absolutely confident I won’t get SHODAN’d and end up crying over a home network catastrophe, never feeling truly secure ever again.
Every now and then it’s tempting to get those fun features in containers like Nextcloud, like public links and federation, but it’s not worth the risk IMHO. Not when there’s state-class adversarial bots written by stupidly smart people roaming the landscape. <_<
I set this container up yesterday. Technically it’s running. But all the settings are in the fucking sql db, and I know fuck all about sql other than drop tables is funny meme from xkcd. But also, ignoring the settings, I would like to point out that there is effectively no client. I mean, there are two official ones - the depreciated one, and the alpha one, and the alpha one has a total of 4 releases with the newest being two years ago. How do you deprecate a client when the server is still in alpha? What the fuck? And on all pages it screams ‘this is alpha testing software, do not use as a daily’. Also the docs are, uhh… rough. If rough was falling 4 stories into a bed of poisonous cacti. It took me 3 hours to get the container running properly and finally poking at the db. It’s as organized as my bedroom (‘it’s somewhere in this dresser, I think…’).
The idea, the potential, is brilliant. Literally everything about getting it working though…
Lots of great software ideas out there. It’s always the execution, availability of resources, and the reality of capitalism getting in the way.
Until I get in the way of capitalism (with a shotgun)
You can use the WebCord app for Spacebar.
I don’t see any options or mention of changing instances, beyond discord canary and public testing…? I might be blind
Containers = Yet Another Attack Surface.
So you’re offering to manage my ~40 services, and make sure that all the dependencies are met - and none conflict…?
I mean, I enjoy hosting things myself, but I’m not going to invite issues that have been resolved by simple solutions. I’ve been around the block with dependency hell, fuck all of that. Now if I was getting paid like 6 figures instead of zero, sure boss, whatever the fuck you say boss, job security all day long. But unless you’re offering, I’m sticking with the easy way.
I mean, that’s true regardless of how it is running. If the service is externally available, it will be probed for vulnerabilities. At least with a container, you can ward off what files it has access to, so an attacker can’t just ransomware your entire NAS with a single vulnerable service.
And thaaaat’s why it’s head/tailscale or nothing for me. I’m smart enough to know I don’t know enough to be absolutely confident I won’t get SHODAN’d and end up crying over a home network catastrophe, never feeling truly secure ever again.
Every now and then it’s tempting to get those fun features in containers like Nextcloud, like public links and federation, but it’s not worth the risk IMHO. Not when there’s state-class adversarial bots written by stupidly smart people roaming the landscape. <_<
Eh, containers are fine if you know what you’re doing. Just run them in a VM if you want more isolation.
Definitely not for the average user though.