tomWhy did you choose ejabberd over other server software bowlofeggs ?
bowlofeggstom: 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
bowlofeggsI can't say I did an extremely thorough analysis, but I've been running it for years and it works great
bowlofeggsI actually maintain the ejabberd package in fedora now too
tomsure. I Understand that. But would you say Prosody fulfills those of at least being easy to deploy and having good XEP support now?
tomI'm not sure how Prosody was years ago, As I've only recently been hosting my own XMPP
bowlofeggsI haven't tried prosody so can't comment on its deployment ease, but I'd expect it also checks the xep and activeness boxes
bowlofeggsAs a programmer I do think that Erlang is a pretty great choice for a messaging server too
bowlofeggsIt's a language that specializes in that
bowlofeggsSo that was attractive too
bowlofeggsI'm not an Erlang programmer myself, but I appreciate "right tool for the job" thinking
tomreally? 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
tomsorta how C is certainly fast and flexable, but for some tasks a simple BaSH script is more than adequate
bowlofeggsErlang isn't a fast language either, but it specializes in message passing and distributed computing
bowlofeggsIt's more that I appreciate the engineering choice behind the decision to go with that language
bowlofeggsErlang makes it easier for applications to scale
bowlofeggsSome of the largest messaging networks in the world use Erlang
bowlofeggsIirc tmobiles SMS is all done in erlang
bowlofeggsBut that's just me appreciating an engineering choice, remember
tomI 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
tomcoming 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
bowlofeggsAh. Well I personally thought it was pretty straightforward to deploy, but ynmv of course
bowlofeggsHow did they deploy? Distribution package? From source?
bowlofeggsYour mileage may vary
tomI don't know
tomI mostly deploy my Prosody from OpenBSD
tomthere's a package for it in OpenBSD
bowlofeggsIt might be harder if they needed to deploy from source, but if they use a distribution package it should be fairly straightforward id think
bowlofeggsThe only real effort I put into mine is keeping the fedora package itself up to date, since I'm the maintainer
> 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?
tomI don't think they were coding XEPs themselves, more just enabling features
tomagain, I didn't ask for details
JonnyI installed ejabberd the first time with 18.04, and compared to postfix and dovecot it was easy to setup 😁
JonnyIt'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
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
tomI'l send them that link
Licaon_Ktertom: but then again, if they chose something like aenigma to "ease" their setup and digged themselves a bigger hole....