XMPP gang rise up! There are dozens of us!
starkzarn
I'm all about adding to the proverbial arsenal. 🤘
You're absolutely right! I'd point you back to my notion of cost-benefit analysis. Anything more than the 20min that I've spent on analysis so far isn't worth my time. If the VM falls over permanently, that was a risk and my time savings has already been worth that risk. If I were looking at something like a production file server or domain controller, sure -- I'd spend more time on it. Likely though, I'd just have engineered it better in the first place. Not every problem warrants a high precision solution. 🙂
I'd be interested in seeing that, or at least knowing which ejabberd container you chose and why.
I'm now morbidly curious for my own sake...
Sort of liminal space vibes
Amazing writing yet again. Appreciate the sharing you do here. You're a god damn gentleman and a scholar.
You haven't mentioned your distro. Are you using systemd-homed? There are some footguns there that can manifest like this.
As another poster mentioned, btrfs quotas or subvolume allocation could be a favtor as well.
Hey thanks so much for the engagement. I was trying to run it on a VPS that cost $35/year. 2GiB of RAM wasn't quite enough to make it work for me, granted that was with the webserver and ancillary supporting services.
I'll find an opportunity to test it out though, as rybbit looks great. I appreciate the mention on the other FOSS products, that's a good look for you. I have plenty of experience with umami already. Cheers!
I'll add to the pile: https://roguesecurity.dev/blog/xmpp
Prosody gets my vote as well for extensibility over snikket and still being relatively easy.
My guide caters more towards OCI runtimes if you're into that. I like podman and quadlets, but you could do docker as well.
XMPP for the win!