I can’t do XMPP. I just can’t. It’s so fucking complicated, uses a bazillion ports I have to punch into my firewall and all kinds of stupid bits of configuration that you really don’t give two shits about for a small instance.
Sorry XMPP enthusiasts, I just can’t even. 🤦♂️
Too hard™
@prologic@twtxt.net maybe try ejabberd? I’ve heard that’s the easiest one to maintain (and probably way less of a pain than prosody)
@novaburst@twt.nfld.uk Does it still requires all these silly ports to be open in my firewall? 🤔
@prologic@twtxt.net wellll, for a bare-bones setup only 5222 (client-to-server) and 5269 (server-to-server) need to be opened.
@novaburst@twt.nfld.uk sigh Why couldn’t XMPP have used the HTTP transport 😢
@mckinley@twtxt.net Uggh I remember this (BOST) back in the ‘ol days when XMPP was “cool” 😅 /me sigh – It’s still all too complicated.
admittedly ejabberd’s Docker image actually looks pretty simple to use and operate (https://hub.docker.com/r/ejabberd/ecs) – I might try this 🤔
@mckinley@twtxt.net Honestly, I appreciate your offer, but I’ve given up on this. I’ve spent ~2hrs on this already looking at ejabberd, got it running and got Beagle-IM to connect to it. Then realised how fucking hard it’s going to be to configure ejabberd properly in production. I’ve looked into Prosody which @jan6@twtxt.net on IRC also mentioned, but getting that working properly in my infra is also going to be “too hard”. They “claim” to support Let’s Encrypt certificates for example, but expect you to run certbert
on a server somewhere 🤦♂️ – I give up 😢
@mutefall@twtxt.net Oh! Yes please! I’d like to take a look at that 👌 Did you also manage to get Let’s Encrypt working in your cluster in some sane way? 🤔