Meta built this under the Digital Markets Act (DMA), maintaining end-to-end encryption (E2EE) and some basic privacy guarantees. As a whole: you can talk across platforms without sacrificing security. (or WhatsApp's definition of it)
@mpanhans @techlore @xmpp well, the Problem with their "solution" is: everything still remains in the WhatsApp silo.
True interoperability would split the userbase onto different servers/providers and the huge pile of data WhatsApp is sitting on and their market power would shrink.
Of course the don't want that even if it would be good for society as a whole.
@mpanhans @techlore @xmpp more details: they reached out in February 2024. I deliberately misunderstood them, pointed them to the XMPP RFCs and told them I'm really exited that they finally want to implement true interoperability.
I even told them that the community would be happy to help sorting out the protocol differences and would even accept new XEPs closing gaps between the two systems.
I never heard back from them 😂
@mpanhans @techlore @xmpp the proof that WhatsApp is based on Xmpp and using ejabberd can be found here by the way: https://web.archive.org/web/20230316112202/http://lists.jabber.ru/pipermail/ejabberd/2009-June/005027.html
@Monal Amazing
@mpanhans @techlore @xmpp A few years ago whatsapp asked me, if I wanted to be one of the early adopters of the new interoperability and add it to Monal, the iOS/macOS #xmpp client I maintain.
But here is the culprit: its not interoperability on the protocol or server level. WhatsApp only provides an http api endpoint you can use to send messages into the WhatsApp "network".
Essentially this allows to write new WhatsApp front ends/3rd party apps. That's not what I'd call " interoperability ".