5 ms·
It would be nice if I could, say, post a picture or an emoji in one xmpp client and have it displayed in all other clients that are capable of sending emojis an
by aidenn0 5y ago
It would be nice if I could, say, post a picture or an emoji in one xmpp client and have it displayed in all other clients that are capable of sending emojis and pictures. XMPP has so many ways of doing both of those that if you're not both using the same client it's a total crapshoot.
Also the desktop clients are garbage:
- Libpurple is such a lowest-common-denominator implementation that lots of features I expect from XMPP tend to just not work (maybe there's configuration buried somewhere in pidgin to make them work, but I haven't found them).
- Psi got abandoned and so has like a dozen forks, some of which sometimes work; and many of which look a bit sketchy
- Gajim is almost great. However its a plugin-based system and too few plugins are enabled by default, so out-of-the-box it doesn't work quite right.
- Dino is getting to the point where it is usable, but if history is any clue, it will be abandoned shortly.
There used to be some promising BOSH clients that could be served as static JS to make a usable web client, but they are quickly becoming out-of-date.
- bertman 5y agore. web client: converse.js (https://conversejs.org/ https://conversejs.org/) is pretty cool!
- MattJ100 5y agoXMPP 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 agoConverse.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 agoRE: 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.
- aidenn0 5y agoRe: 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
- ATsch 5y ago> It would be nice if I could, say, post a picture or an emoji in one xmpp client and have it displayed in all other clients that are capable of sending emojis and pictures. I don't personally think multi-device will ever be solved in a satisfactory way in XMPP. Like IRC, the whole architecture is fundamentally based on relaying messages. This works great for desktop computers, but as you add more devices with more intermittent connectivity, it breaks down quickly as you need to resort to hacks like sending deltas to other devices as carbon copies, which may or may not be delivered or interpreted correctly by clients. To solve it you need to fundamentally rethink your protocol not as one that relays messages, but synchronizes history. This is extremely hard to do without breaking backwards compatibility as you basically need to rearchitect every part of the stack. Matrix is a notable open messaging standard that does this and although it has it's flaws, multi-device experience is not one of them. I'd definitely welcome XMPP making improvements in this area, but I'm not personally optimistic it can be done in time considering the generally dwindling userbase.
- swiley 5y agoI run dino on both my phone and desktop and have zero problems with message carbons on both.
- aidenn0 5y agoJabber has almost completely solved this. TFA mentions how and notes the two places that have in-progress XEPs for improving (there's a race with MAC/Carbons where you have to either risk duplicate messages or dropping; current recommendation is to do the former and check for dupe). On top of this, by far the best client I've used for XMPP is Android-only (Conversations.im). I have no problem using Gajim on my desktop and Conversations on my phone, and I have an SMS/MMS bridge (jmp.chat) that lets me send even to people without jabber from it. Multi-device and mobile is the one place where XMPP is ahead of 99% of the other messages, and it works similarly well to Matrix in my limited experience with Matrix.
- ATsch 5y agoIn 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.