Hacker News new | past | comments | ask | show | jobs | submit login

btw. very much agree most of the clients are inadequate but if I could humbly pimp Openfire (I'm a dev there): https://github.com/igniterealtime/Openfire

And ejabberd of course (powering WhatsApp): https://github.com/processone/ejabberd

You'll see that on the server side at least XMPP is very well catered for.




What are the advantages of OpenFire over ejabberd/prosody?


Super easy to use, nice admin pages, great plugin architecture for 3rd party developers to extend its functionality. Means there's a LOT of cool plugins which add video, screen sharing, chat archiving, etc.

Deal breaker against it (depending on your use case) is lack of support for multiple domains. It can only handle one per deployment.

It also does need at least 512MB RAM which rules it out on embedded devices.


I've used both and moved on to prosody. Ejabberd is just too arcane to configure and debug; and openfire is a damn resource hog for no apparent reasons.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: