XMPP Service Operators - 2019-05-06

Anybody run ejabberd?

tom: me

how many users do you have bowlofeggs ?

Very few, maybe 5-7. Not for business

Why did you choose ejabberd over other server software bowlofeggs ?

tom: it was years ago so I don't recall all the analysis, but I liked that it was easy to deploy and had good support for various XEPs, and that it is active

I can't say I did an extremely thorough analysis, but I've been running it for years and it works great

I actually maintain the ejabberd package in fedora now too

sure. I Understand that. But would you say Prosody fulfills those of at least being easy to deploy and having good XEP support now?

I'm not sure how Prosody was years ago, As I've only recently been hosting my own XMPP

I haven't tried prosody so can't comment on its deployment ease, but I'd expect it also checks the xep and activeness boxes

As a programmer I do think that Erlang is a pretty great choice for a messaging server too

It's a language that specializes in that

So that was attractive too

I'm not an Erlang programmer myself, but I appreciate "right tool for the job" thinking

really? I'm not faimiler with Erlang, but Prosody being written in Lua, I know that Lua is certainly not the fastest language in the world, about on par with Python, albeit slightly less hand holding and more flexability, it certainly fast enough for most things and more than adequate for hosting at least a couple hundred users

sorta how C is certainly fast and flexable, but for some tasks a simple BaSH script is more than adequate

Erlang isn't a fast language either, but it specializes in message passing and distributed computing

It's more that I appreciate the engineering choice behind the decision to go with that language

Erlang makes it easier for applications to scale

Some of the largest messaging networks in the world use Erlang

Iirc tmobiles SMS is all done in erlang

But that's just me appreciating an engineering choice, remember

I ask because I know someone trying to setup their own XMPP server for themselves and a few friends, and they chose to do that with EjabberD. They seem to be having a lot of trouble doing so, and spending a significant amount of time implementing more XEPs as they find they need them, or even just setting up crypto properly

coming from a Prosody background, I couldn't see why the choise of ejabberd was made since this person was not trying to host 100,000 users

Ah. Well I personally thought it was pretty straightforward to deploy, but ynmv of course

ynmv?

How did they deploy? Distribution package? From source?

Your mileage may vary

I don't know

I mostly deploy my Prosody from OpenBSD

there's a package for it in OpenBSD

It might be harder if they needed to deploy from source, but if they use a distribution package it should be fairly straightforward id think

The only real effort I put into mine is keeping the fedora package itself up to date, since I'm the maintainer

https://upload.nuegia.net:5281/upload/RGn9wDjzkDcbJHQG/02%20Force%20Legato%20System.flac

tom: > They seem to be having a lot of trouble doing so, and spending a significant amount of time implementing more XEPs as they find they need them, or even just setting up crypto properly They are coding missing XEPs? Which ones?

I don't think they were coding XEPs themselves, more just enabling features

again, I didn't ask for details

I installed ejabberd the first time with 18.04, and compared to postfix and dovecot it was easy to setup 😁

It's not as easy as a simple web app with a db but if you just adjust the default config where needed then it's OK

tom: The out of the box config ( https://github.com/processone/ejabberd/blob/master/ejabberd.yml.example ) should give you close to 100% on compliance.conversations.im

I'l send them that link

tom: but then again, if they chose something like aenigma to "ease" their setup and digged themselves a bigger hole....

Hi

Medications: yo

hi