4 ms·

XMPP is fully Unicode-aware and always has been, so clients lacking emoji support are probably due to platform-specific issues. I'd be interested in specific ex

XMPP is fully Unicode-aware and always has been, so clients lacking emoji support are probably due to platform-specific issues. I'd be interested in specific examples if you can name names. libpurple (and derived clients such as Pidgin) have been lacking in XMPP love for some time, they've been focusing on more fundamental changes within the project. There are signs things may be improving, but unfortunately it's only a good example of XMPP in 2006. Things have moved on. As you say, Gajim and Dino are good modern clients, and actively developed. I see no evidence of either of them being abandoned any time soon. Converse.js and JSXC are actively-developed web clients. JSXC just received an EU grant to implement group audio/video calls.

aidenn0 5y ago
Converse.js was "the best at the time" when I tried about a year ago. I just tried it now and it is far improved, so that's good. JSXC was so-so when I tried a year ago. They seemed to be more focused on "Add XMPP to your web-page/webapp" rather than "use as a standalone" and a lot of the UI decisions seem informed by that (it very much tries to only use a fraction of the display, and managing more than about 3 chats starts to get crowded). Perhaps with theming I could make a good standalone app out of it, but it feels like swimming upstream. [edit] Didn't address your comment on Dino; I don't see any signs of it being abandoned either, this is more my cynical rule of "every time a jabber client gets stable enough that you can use the one from your distro's package manager, it gets abandoned" it's purely empirical and Gajim is the only exception to it so far in the past 20 years.
aidenn0 5y ago
RE: emoji Not all clients send unicode emoji; some send their own emoji, as the clients emoji support predate's unicode's emoji support (2010). Psi is one example off the top of my head.
- mst 5y ago
  (Y)
  - Lammy 5y ago
    :putnam:
aidenn0 5y ago
Re: images Sending an image from one client software will always result in either an inline image or a link to the image being displayed in other client(s). However there are combinations of clients which won't expand inline images from each other (IIRC conversations.js 6.x and dino seem to do things slightly differently, while conversations.im views both just fine). Then there's the fact that not all Jabber clients will convert to jpeg, so e.g. in my Dino chat history I have a bunch of WebP images that don't expand inline, but show fine on Gajim and Conversations.im

aidenn0 5y ago

Converse.js was "the best at the time" when I tried about a year ago. I just tried it now and it is far improved, so that's good. JSXC was so-so when I tried a year ago. They seemed to be more focused on "Add XMPP to your web-page/webapp" rather than "use as a standalone" and a lot of the UI decisions seem informed by that (it very much tries to only use a fraction of the display, and managing more than about 3 chats starts to get crowded). Perhaps with theming I could make a good standalone app out of it, but it feels like swimming upstream. [edit] Didn't address your comment on Dino; I don't see any signs of it being abandoned either, this is more my cynical rule of "every time a jabber client gets stable enough that you can use the one from your distro's package manager, it gets abandoned" it's purely empirical and Gajim is the only exception to it so far in the past 20 years.

aidenn0 5y ago

RE: emoji Not all clients send unicode emoji; some send their own emoji, as the clients emoji support predate's unicode's emoji support (2010). Psi is one example off the top of my head.

mst 5y ago
(Y)
- Lammy 5y ago
  :putnam:

aidenn0 5y ago

Re: images Sending an image from one client software will always result in either an inline image or a link to the image being displayed in other client(s). However there are combinations of clients which won't expand inline images from each other (IIRC conversations.js 6.x and dino seem to do things slightly differently, while conversations.im views both just fine). Then there's the fact that not all Jabber clients will convert to jpeg, so e.g. in my Dino chat history I have a bunch of WebP images that don't expand inline, but show fine on Gajim and Conversations.im