As a community, we often ask ourselves how to attract more users to #XMPP. Yet the real tragedy is that people would rather build something entirely new (loosely based on email or #ActivityPub) than consider XMPP. Need end-to-end encryption by default? If compatibility with existing XMPP clients is a secondary concern, you can implement it in your own solution while still benefiting from our two decades of experience in instant messaging.
I consider this a failure on our part but I don’t really know what to do about it. Most arguments against #XMPP don’t hold if you’re building from scratch anyway:
• #Conversations_im looks very outdated: OK, but you are developing your own clients anyway.
• XMPP doesn’t have an SDK: Neither does your #ActivityPub or email stack
• OMEMO is insecure and I would prefer #MLS: Yes, let’s work on that together and you’ll still benefit from XMPP’s 100+ solved IM problems.
Hi, for XMPP/AP Bridge you can simply use it by following the bot account @xmpp_bridge from a fediverse account (conversely from XMPP). Try it out if you want!
@debacle@daniel Ages ago, people created gateways between different transport protocols. Many application protocols even had/have explicit support for them.
MLS (or OMEMO or …) messages could cross boundaries: Adressing one of my contacts by email, the other via Fediverse, the third on XMPP, the fourth by phone number, …
IMHO, the point of both Delta and the new ActivityPub based chat (does it have a name yet?) is prevalence, at least in a certain part of society.
I remember, that Delta proponents said, that "you can reach everyone, who has an email address."
Now it is: "You can reach everyone, who has a fediverse account."
In the end, it is not that easy, e.g. because email users might not have autocrypt in their client, and it will take a while until there is #MLS in e.g. #mastodonEl.
@daniel conversations outdated?? It's the client I like the most. It's the only mobile client that just works and has a greate UI. If people want something better they should be contributing...
@daniel@pixelschubsi@tris I don't know much about Google, but in ActivityPub identity is an URI and it can't be used across multiple protocols. It can be linked to other identities, but this is not the same as single identity.
For example, while working on my ActivityPub project, I have to use 3 additional communication protocols: Matrix and XMPP (for group chats and encrypted messages), and E-mail (for notifications). This is ridiculous! I want a single identity and a single application for everything.
@silverpill@pixelschubsi@tris you can have a single account (or as I phrased it 'identity and login credentials') across different protocols. For example your Google account works across multiple protocols. And even in the federated world we have several cases where email address == xmpp address. So to repeat myself: using the same identity is good. Doesn't mean you are locked into ActivityPub if you want to build instant messaging.
@pixelschubsi@tris Yes, agreed. Tremendous value in reusing identities and login credentials. Big skepticism with regards to using AP as a protocol. One can probably kinda make it work… But why? What’s the benefit?
@daniel@tris I'm also genuinely surprised that people believe that ActivityPub, a protocol even named after its purpose, to publish activities, is a good protocol to pursue private instant messaging. The goals of those two couldn't be more detrimental.
I do see a purpose of being able to reuse your "ActivityPub identities", which actually are just WebFinger identities. Maybe someone should specify how to discover XMPP accounts via WebFinger and push that as a solution for AP messaging?
@tris there are three actively developed protocols for federated instant messaging (XMPP, Matrix, Deltachat). At least one of them is very open to new developers and new ideas and has a structure in place to collaboratively work on those ideas and bring various stake holders together. With no disrespect to that individual I don't see why there needs to be a forth protocol loosely based on ActivityPub.
@tris two things: I already said in my follow up post that if someone wants to build their own clients on top of XMPP and prefers MLS over OMEMO, the XMPP community is very open to that. A protocol is much more than just the encryption. They would still benefit from all the other things XMPP has solved.
A lot of what's in that blog post is ill-informed and bordering on disinformation and fear mongering.