3 ms·
A few weeks ago I replaced a XMPP chat architecture with socketio. It's so much better for my needs (website with realtime chat). There were 2 main reasons in
by estefan 11y ago
A few weeks ago I replaced a XMPP chat architecture with socketio. It's so much better for my needs (website with realtime chat).
There were 2 main reasons in the end:
- No way to log all messages sent to a database so that users could retrieve them on subsequent logins
- No way to edit/delete messages, especially in multi-user chats.
Maybe these things are possible, but I couldn't find how to do it. Now, with socket IO on nodejs, I have a < 400 line chat server with DB integration that is much more suitable for my needs.
I guess XMPP's focus was too narrow.
- daurnimator 11y ago> - No way to log all messages sent to a database so that users could retrieve them on subsequent logins This is what MAM does.
- estefan 11y agoPerhaps the ejabberd support is bad or poorly documented? Either way I just couldn't find how to do it. All I could find for MAM was logging to flat files.
- rakoo 11y agoThis post [1] seems to indicate that ejabberd's support of MAM is complete. Note that you also (obviously) need support from the client, which most but not all clients do. Conversations [2], on mobile, does. [1] https://blog.process-one.net/ejabberd-15-06/ https://blog.process-one.net/ejabberd-15-06/ [2] https://play.google.com/store/apps/details?id=eu.siacs.conversations https://play.google.com/store/apps/details?id=eu.siacs.conve...
- estefan 11y agoThat sucks. I searched for ages but found nothing. Oh well, it only took me a couple of days to replace it, so it's not the end of the world.