I don’t know what I was expecting but it looks more and more like the Messaging Interoperability the EU promised will be each gatekeeper essentially publishing their client to server protocol and then you can either use multi protocol messengers or transports. No s2s federation.
Looks like one might be able to log in through the (propriety) c2s API with third party IDs though.
Discussion
Loading...
Discussion
@daniel that's sad but not unexpected.
Another point of view is to work with small actors to build that together.
And I think of course to #XMPP and #matrix and #Sip but also to #threema #wire and #deltachat for example!
Having a working instant messaging operability between open source actor looks like a good first step, isn't it?
Hi @daniel
sorry I see now that your post is from 2023 !! No idea why I saw it today in my timeline ^^'
@j12t @lascapi Meta has a proprietary HTTP API that allows you to send and receive messages to and from WhatsApp and Facebook Messenger users. You can get access to that after signing a contract with Meta. Two (relatively unknown) IM companies are taking them up on that and EU users will soon be able to send e2e encrypted messages to those third party IM networks. A very high level overview of that API can be found on the internet but details are NDA'ed.
@j12t @lascapi The EU asked various stakeholders on how they imagine the interop to work. I advocated for opening up the s2s link using either XMPP or a standardized protocol with similar properties. Meta advocated for what they are doing now. I guess their arguments were more convincing.
It's less malicious compliance rather than they helped write the law.
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled