@MDT

Unos clientes de #fediverso pueden usar un link de este formato:

xmpp:[email protected].org?join

Así es solamente un clic 😉

#Jabber #XMPP #radio #mexico

@jae @gnemmi

Can't wait to try your XMPP-Delta bridge!

Is there a public repo somewhere?

My vague impression is:

Delta is focussed on private chats (individuals, small groups) and has its strength there.

#XMPP is deliberately a universal protocol for everything: private chats, team chats, public chats, social. In my company we even built an IoT product based on it!

Still, some #Jabber clients are focussed: #Conversations_im on private chats, #Movim on team chats and social features etc.

@debacle @gnemmi

> Yes, Delta is mainly made by a German company, so they have more or less the complete project in their hands. All clients are based on exactly the same library. That gives a nice "out-of-the-box" experience.

yip, i work on the project the gerrman's have built the ecosystem to use the common core. it's fairly robust and has allowed me to write a tui for #deltachat

i've also created an xmpp <---> deltachat bridge in go that's almost ready to release (working on the omemo part still).

> #Jabber/#XMPP is a huge and diverse ecosystem with sometimes conflicting interests or priorities. And it's an open standard with many implementations, which can result in incompatibilites.

true, but the fact that we have this battle-tested protocol and you can build on is really nice.

@gnemmi @smn

Speaking from a #Jabber/#XMPP fanperson perspective, the downsides are:

1. No good client with A/V calls for Windows. #Gajim by @gajim is on the MS store and is good, but doesn't have A/V calls, #Dino by @dino is also good, has A/V calls, but only has outdated Windows installers somewhere on the net. There is #Movim by @movim, but web clients are not everyones cup of tea. Problem can and will be solved, but atm. it is a drawback. Maybe #Kaidan by @kaidan will solve that.

@jae @gnemmi

Yes, Delta is mainly made by a German company, so they have more or less the complete project in their hands. All clients are based on exactly the same library. That gives a nice "out-of-the-box" experience.

#Jabber/#XMPP is a huge and diverse ecosystem with sometimes conflicting interests or priorities. And it's an open standard with many implementations, which can result in incompatibilites.

I prefer the latter, because I see more advantages in that approach, but YMMV.