Hacker News Reader

Comment by jaimehrubiks | Hacker News Reader

Until recently I wasn't aware that the XMPP protocol specification was still being updated and up to date including things like read receipts, message reactions etc. I'd love to see the EU standarize communications with something like XMPP and something similar for voice/video. It would be amazing to not depend on clients like WhatsApp for my whole life.

I'm excited to try Movim and mobile XMPP clients with XMPP bridges like the one in the front page last week.

View on HN

There was one beautiful moment where Google and Facebook supported XMPP so you could just set up your XMPP server and talk with people across the platforms but both decided to close their gardens for the usual reasons

But XMPP is shitshow of million XEPs and massive matrix of which supports what. So just because in theory there is some feature you want it doesn't mean that your server and your client will work with it. That's terrible value proposition to anyone wanting to do anything in the space, you dont want to debug (and we did had to, when we used xmpp for our company chat) why user X using communicator Y on platform Z can't send attachment to your user on communicator Q.

XMPP needs to just sit the fuck down, gather the XEPs and put it into XMPP 3.0, with few feature sets that every client and server using it needs to support all at once, not picking and choosing.

So if you make text only chat client, it supports all of the formatting, all of the file send/receive, all of the MUC things, all of the E2E encryption things, all at once. And have one text formatting to support (Markdown seems to be winning here), not a bunch.

> gather the XEPs and put it into XMPP 3.0

The yearly compliance suites try that - and then IMHO fail a bit by offering too many variants.

What variants do you think should not be included?

That's of course the tricky question. To a degree it might be a presentation thing that they are all shown equally.

E.g. to me, I'd expect a headline profile that's equivalent to "Advanced IM + Advanced Mobile". And I'm not sure the split into "Basic/Advanced" esp for mobile makes much sense. But I also can totally understand why people thought each of the distinctions was valuable, but that makes it feel a bit too comittee-style of trying to make everyone happy by including their variant and over-complicating the entire thing as a result. Certainly something I've seen happen to other specifications.

https://docs.modernxmpp.org/

I think I've seen a comic about this.

> XMPP needs to just sit the fuck down, gather the XEPs and put it into XMPP 3.0, with few feature sets that every client and server using it needs to support all at once, not picking and choosing.

Matrix: https://spec.matrix.org/latest/

You are welcome

This isn't compatible with XMPP.

> gather the XEPs and put it into XMPP 3.0, with few feature sets that every client and server using it needs to support all at once, not picking and choosing.

They do exactly that - https://xmpp.org/extensions/xep-0459.html

Easy to deploy solutions for common use cases like company chat are being worked on with projects like https://snikket.org/ (or well movim!)

Yes, extensibility is XMPP’s curse. Don’t make something open and extensible for communication. Make it full featured and versioned so that users don’t have to deal with a stupid compatibility matrix.

I hated XMPP with all my heart.

Figured I'd chime in how pleasantly surprised I was with how well xmpp works for my narrow use case of an e2ee messenger between family members. Snikket is packaged with STUN/TURN out of the box, and to my surprise, a lot of family calls are going through the xmpp client. Perhaps there are pain points that I don't see, but xmpp's method for audio/video jingle works well.

Unfortunately, I haven't yet found a mobile XMPP client that has the same features as Movim.

For example, conversations.im still lacks Message Reactions, Threads, and Publish-Subscribe:

https://github.com/iNPUTmice/Conversations/issues/3874

https://github.com/iNPUTmice/Conversations/issues/3303

https://github.com/iNPUTmice/Conversations/issues/1642

That's sad. Specially reactions which is more chat/conversation oriented.

XMPP is also integrating audio and video conferencing, there is even some bridges with SIP available to be compatible with VoIP.

What are the options for jingle <-> SIP?

I'm unclear if ejabberd mod_sip is actually a bridge or something else entirely and jigasi seems pretty jitsi specific.

Reply on news.ycombinator.com