

XMPP gang rise up! There are dozens of us!


XMPP gang rise up! There are dozens of us!


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.
Paperless-ngx! https://github.com/paperless-ngx/paperless-ngx
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!