XMPP: The Gem of Instant Messaging
41–50 of 138 posts
Re: XMPP: The Gem of Instant Messaging
#42I think the big issue with XMPP are the clients. Element is so much better that it's hard not to recommend Matrix to people despite its bloat and metadata leakage problems. JMP/Snikket for tying a normal phone number to your XMPP @ are really convenient, but the clients remain a problem. Plus, SIP dialers are not supported on IOS afaik. I am really surprised there isn't a venture backed company pushing XMPP forward.…
> I am really surprised there isn't a venture backed company pushing XMPP forward. Maybe people have tried and realized it's not viable.
Actually, WhatsApp would fulfill your definition there. They are/were a startup whose entire product/platform is an xmpp client (using their centralized server/instance). Now, whether they pushed "xmpp forward", or merely would be considered pushing a chat platform and who cares whats under the covers...well, that i leave as an exercise for you or others to decide/opine. ;-)
Re: XMPP: The Gem of Instant Messaging
#43Mandatory blog post on XMPP and decentralized protocols: https://signal.org/blog/the-ecosystem-is-moving/
So, it's not such a gem?
Re: XMPP: The Gem of Instant Messaging
#44Earlier quoted context omitted.
The modern equivalent to XMPP is XMPP. Like every other healthy and alive protocol it evolves over time to meet new needs.
Given the context above, does that mean the modern version is no longer "overcomplicated and hard to implement?"
Re: XMPP: The Gem of Instant Messaging
#45Re: XMPP: The Gem of Instant Messaging
#46Re: XMPP: The Gem of Instant Messaging
#47I've recently looked at the suite of protocols underlying RCS (or so at least I think; the standards landscape is as confusing as ever), and it's baffling how the industry ended up with that when XMPP was... just there . The contortions they had to do to cram server-based federated instant messaging into the context of the SIP protocol stack by sheer force are something to behold. I can only assume this is entirely b…
Re: XMPP: The Gem of Instant Messaging
#48XMPP was not a mobile friendly protocol for a while, had efficiently no security out of the box and lacked simplest things like image or other file transfers.
Re: XMPP: The Gem of Instant Messaging
#49XMPP was not a mobile friendly protocol for a while, had efficiently no security out of the box and lacked simplest things like image or other file transfers.
"Hey, I want to set up a modern messenger."
"Sure! Here's XMPP, the ten extensions you need to enable and configure (problem left as an exercise for the reader), and the seven ports you need to open!"
"... Okay? A Matrix node is apparently a drop-in solution; I'm gonna use that."
XMPP is in desperate need of a Docker image that Just Works and the wizard to set up that Docker image. And then you need users savvy enough to have their clients configured correctly.
Re: XMPP: The Gem of Instant Messaging
#50I think the big issue with XMPP are the clients. Element is so much better that it's hard not to recommend Matrix to people despite its bloat and metadata leakage problems. JMP/Snikket for tying a normal phone number to your XMPP @ are really convenient, but the clients remain a problem. Plus, SIP dialers are not supported on IOS afaik. I am really surprised there isn't a venture backed company pushing XMPP forward.…
I think there's a tendency to dismiss this argument in the XMPP community (but there's a lot of truth to it, I choose to use the XMPP desktop clients but none of them are as nice to use as any big commercial IM providers client), but also a tendency for people to make this argument without realizing that they're comparing open source projects run by one or two people to VC funded projects with a company backing them. Of course Discord or Element or whatever will be "better" in some ways, they have a team and millions of VC funding behind them. However, one of the many reasons I chose to use XMPP back in the day when I was first evaluating whether to use it or Matrix, and one of the big reasons I got more heavily involved in the community later, was specifically because the standards body wasn't strictly tied to a company looking for VC funding (and all the individual client/server projects I've contributed to are the same). But, this does mean there aren't really any clients that I'm in love with (but there are clients for every random niche platform imaginable, which I think is probably more important personally).
All that being said, try Snikket if you haven't. It's relatively new, but I think they're really doing a good job of creating a suite of clients that can be recommended to "normies" who don't want to sacrifice shiny graphics for the sake of using something that's a bit more free from VC influence.