4 ms·
XMPP is a bit complex, and suffers from some problems derived from too much flexibility. The mandatory part of the protocol is too small. This could be fixed by
by nextos 9y ago
XMPP is a bit complex, and suffers from some problems derived from too much flexibility. The mandatory part of the protocol is too small. This could be fixed by creating a meta XEP that lists all XEPs needed by modern clients.
However, it's a very capable protocol. Just see how nice conversations.im is. It doesn't even use GCM, and both latency and energy usage are fantastic.
- ossguy 9y agoSuch a meta XEP exists already: https://xmpp.org/extensions/xep-0387.html#im https://xmpp.org/extensions/xep-0387.html#im If you use a client that conforms to the Advanced Client requirements of the IM and Mobile Compliance Suites (with a similarly up-to-par server), you will have a very good experience.
- detaro 9y agoRecommendations for good clients for desktop systems? Maybe my google-fu is particularly weak today, but I couldn't find a clear statements which clients outside conversations.im fullfill those (obviously only the IM suite, since mobile wouldn't apply)
- ossguy 9y agohttps://gajim.org/ https://gajim.org/ tends to be best for desktop (binaries exist for most desktop OSes). For macOS, you may want to try Adium or Psi. Or you can use https://movim.eu/ https://movim.eu/ which, though a web client, has fairly good feature support as well.
- Shoothe 9y agoI second Gajim especially 1.0.0 version that looks good. There is also https://dino.im https://dino.im but that's still in alpha.
- nextos 9y agoThe problem is that selection is still limited if you factor in OMEMO support (end-to-end encryption): https://omemo.top/ https://omemo.top/