4 ms·
In my experience (which was echoed by coworkers requests to resend messages, until we switched) there are a select few happy paths where it works reasonably wel
by ATsch 5y ago
In my experience (which was echoed by coworkers requests to resend messages, until we switched) there are a select few happy paths where it works reasonably well and a lot more where it doesn't. You seemed to agree with that in your original comment.
In general the problems with XMPP are rarely with missing checkboxes or things that miraculously don't exist somewhere in the hundreds of accepted and in-progress XEPs, but the long tail of user experience in the real world.
- aidenn0 5y agoLinux desktop clients not named "gajim" were very slow to adopt Carbons as the delivery method. And in Gajim you needed to enable a plugin. Things were very bad in the transition period (which ended about 5 years ago?). At work we setup a jabber server for a small group of about 6 people and then more people started using it. It was running an ejabberd that was too old to support carbons. Once it became clear that some sort of IM solution was wanted, we came up with a list of features. Upgrading ejabberd and recommending proper clients fixed every box except "iOS client with push notifications" (XMPP didn't at the time support out-of-band push notifications, it does now).
- deleted 5y ago[deleted]