A poll to any admins who are self-hosting their own xmppwhat is your server running?

[loremipsum@s.cafe]

A poll to any admins who are self-hosting their own xmpp
what is your server running?

#xmpp #jabber #conversations #selfhosting #poll

[debacle@framapiaf.org]

@loremipsum

I co-admin multiple servers, both #ejabberd by @ejabberd and #prosody by @prosodyim. (We use the #Debian packages.) Selected the latter, because it was my first #Jabber server.

Btw. there is also @tigase.

[zeank@mastodon.social]

@debacle @loremipsum

And MongooseIM.

[maskedwitch@hachyderm.io]

@loremipsum
I have maintained a few different servers over the years. I've mostly stuck to prosody.

[hp@mastodon.tmm.cx]

@loremipsum I have ran openfire in the past. And I will say: Under no circumstances should anyone ever run openfire.

Unless you have like, a huge instance with many many accounts with huge rosters you're gonna thank yourself for using prosody

[neil@mastodon.neilzone.co.uk]

@loremipsum Snikket!

[naln1@ak.angelstrapped.com]

@loremipsum I tried ejabberd first, and it was so difficult to get up and running that I ran to Prosody instead

[walnut@shrimp.thesoftestpaws.net]

@loremipsum
You may already know, but Snikket uses Prosody under the hood. It's like an opinionated config with a few other things already bundled like coturn and cert renewal. People do "hack" their Snikket server but it's usually recommended to run Prosody directly if you want more customization, and it's totally possible to migrate from Snikket to Prosody.

Also about stun/turn I often hear eturnal is nicer to setup than coturn. Both will work fine

[nicoco@pouet.pas.la]

@loremipsum Also note that snikket is written without a C and really is prosody under the hood.

[jee@hostux.social]

@loremipsum prosody on podman https://github.com/jee-r/docker-prosody/

[martin@social.mdosch.de]

@loremipsum@s.cafe
I'm running my #xmpp server with #prosody. If I'd setup my private server today I'd probably choose #snikket.