Has anyone tried this? It’s discord reverse engineered.
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.
Containers = Yet Another Attack Surface.
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.
Why would one use this rather than just using something like Matrix or self-hosted Stoat? I’m not sure what it being “Discord compatible” really gets this project. Bot compatibility is nice, but aren’t most Discord bots closed source anyway?
Because Stoat is also riddled with problems and Matrix is a dysfunctional hot mess.
In the proper timeline the superior proprietary platform Axon beat out Discord.
The cumulative hours we’ve lost screwing around with the manual placement spacial audio on Axon… When it went tits up we switched to Mumble tho
HHhhmm… Do container/docker install option. This is why it’s probably stagnated in adoption from the selfhosted community.
It needs a container based install, no one likes installing dependencies and crud onto their pristine environments any longer.
It’s weird that the server has a .dockerignore file without a Dockerfile.
Seems like they’re working on Docker build actions right now according to some other comments
It’s just not mentioned prominently https://github.com/spacebarchat/docker
last commit 3yrs ago… seems unmaintained
Docker compose’s don’t really need to be maintained though. As long as the app doesn’t need new components old docker composes should work.
EDIT: Oops, it does look like spacebarchat’s docker images have last been updated over 2 years ago:
https://hub.docker.com/r/spacebarchat/server
EDIT2: Although this is outdated, I think their github repo has an action to autobuild docker images on pushes. Still investigating.
EDIT3: Okay, they don’t seem to be actually ran.
But using nix to build a docker image is pretty cool.
EDIT4: Oh shit, the docker image build workflows were added just 2 hours ago. Of course they haven’t been ran!
Docker support soon, probably.
EDIT5: the workflow ran, but it looks like it’s private for now.
You got my heart racing with the twists!
Right? Reading that was like watching an action movie!
3 years of abandonment? Absolutely not.
Where are you getting three years of abandonment from? The branding repo OP linked was last updated 10 months ago, while the server repo appears to have had pretty steady development for the last month at least (as far back as I bothered checking on mobile)
