- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
For self-hosting though, the project I work on - Snikket - uses XMPP but has all the nice modern things you’d expect ready to go right out of the box, more like a Matrix (Synapse/Element) setup. Probably the biggest thing missing for Snikket right now is an official web app (we currently have Android and iOS apps).
My personal feeling is that if you’re looking for something a bit more extensive, “team chat” style (such as Discord, Slack, that kind of thing), you’re better served by Element right now. However if you’re looking for something lightweight and simple for personal messaging in a group of family/friends (e.g. to replace WhatsApp/Telegram/Signal) then XMPP via Snikket is a great choice.
- The above is copied from someone else. Anyone have any experience running this for family / friends?
You can, but honestly no idea how to handle stuff like the certs from that point on. Most other software on docker lets me eg.: just bind-mount the host’s directory with the certs I want to use - or just not even know about SSL in the first place and just let me reverse-proxy the access in (like, say, a simple static page web server).
But, like I said, the last times I tried to get into it, it tried its darnest to get in my way. If that’s changed since then, that’d be great.
There is a docker container setup with automatic lets encrypt and proxy. Can search around for it.
Hmmm maybe that’s the one that tries to do everything on its own instead of using the stuff I’ve already set up. Had similar issues with eg.: Nextcloud.
I’ve been looking for an alternative “the actual XMPP service only, nothing else that can be sourced by the host” container setup but there doesn’t seem to be any.