mastodon - Link to source
Hello Mastodon Family! Lena here from marketing. I'm writing an article on instant messengers with interoperability and I'm looking for some more information on what actually makes a messenger interoperable. I thought of focusing on: Element, Delta, and SimpleX but I'm open to other suggestions! Could anyone kindly advise? ☺️
in reply to Tuta

mastodon - Link to source

veroandi

Maybe XMPP?

xmpp.org/announcements/open-le…


Detailed technical briefing: The Case for XMPP – Why Meta Must Embrace True Messaging Interoperability | XMPP - The universal messaging standard

Introduction The European Digital Markets Act (DMA) was introduced to ensure fair competition and prevent large technology companies from exploiting their dominant positions. A key aspect of the DMA is the requirement for Number-Independent …
xmpp.org
in reply to Tuta

mastodon - Link to source

Houbey

Moin Lena, also #SimpleX sollte auf jeden Fall dabei sein. Finde ich toll, wenn du das tust. Ein immer noch unterschätzter Messenger der auch dezentral gehosted werden kann und meiner Meinung nach "der" Messenger schlecht hin.

Das noch junge Projekt @simplex versucht genau wie Tuta die Privatsphäre und deren Daten ihrer Nutzer und Nutzerinnen zu schützen.

Vielen Dank, für deine Arbeit. 😊🌼🍀

#simplex @SimpleX Chat
in reply to Tuta

mastodon - Link to source

chrysn

When talking about interop, don't let anyone tell you that they can't become interoperable for security reasons: MLS exists, Google and Apple support it for RCS, and Matrix is migrating there.
en.wikipedia.org/wiki/Messagin…

Nothing to tell people who want "just something to use right now", more for an "Outlook" section.

cryptographic protocol for group communications

Contributors to Wikimedia projects (Wikimedia Foundation, Inc.)
in reply to Tuta

mastodon - Link to source

nictakiego

I guess most interoperable from these is Element. You can use it both for daily communication with friends, and for work or working on projects. Most importantly you can self host it, so actually own your data, which is a big plus for it. Yet...for communication with friends I'd still choose Signal, as its more popular, has better performance and privacy mechanisms (in comparison to matrix public instance). Well and for journalists simplex definitely shines. So I'd say it all depends on purpose, but objectively Element has the ability to be any of those 3 if done right.
in reply to Tuta

mastodon - Link to source

erebion

@nictakiego I strongly disagree. SimpleX hasn't proven itself enough to be reliable, while Signal has proven again and again that it can protect journallist in very dangerous regimes.

Matrix has a metadata issue and the way it works means it wastes a lot of energy as well. It is not sustainable.

XMPP is an internet standard, so that's the most interoperable, it's literally defined as such.

@nictakiego
in reply to Tuta

glitchsoc - Link to source

Ben

I could be thinking completely differently than where you are, but I would go for Matrix rather than Element. Element is cool, but it's the protocol behind it (Matrix) that truly makes Element interoperable. Without Matrix being an open and federated standard, Element would just be another closed chat app that doesn't allow people to speak with anyone unless they use Element. With Matrix I can speak not only to anyone on the Matrix network, but also a bunch of other bridged chat protocols. Incredible!
in reply to Tuta

mastodon - Link to source

Russ

Sensitive content

@Delta Chat
in reply to Tuta

mastodon - Link to source

Gorujo

honestly an interoperable messenger has to be the fact that it can communicate across other servers and/or platforms, instead of covering just element, cover the matrix protocol, the underlying and see/cover docs.mau.fi/bridges/index.html and beeper.com/ (beeper uses Matrix for the underlying core too)

Beeper — All your chats in one app

Get the most popular messaging services, all in a single app. WhatsApp, Signal, Instagram, Telegram, and more.
Beeper
This entry was edited (4 days ago)
in reply to Tuta

mastodon - Link to source

erebion

XMPP would be great, of course.

Element/Matrix creates lots of metadata, compared to XMPP, so that does not seem to fit well into the lineup of Tuta.

SimpleX recently did some weird Blockchain stuff, so they're out as well.

XMPP is the internet standard for instant messaging, literally. There's an RFC for that.

Also, there are still not enough pulic (paid?) XMPP services around, so people struggle finding one they trust if they don't self host.

XMPP is reliable as well.

in reply to Tuta

mastodon - Link to source

🌈 Lascapi ⁂

Hello, I see you already had a lots of nice answer.

Here is my point of view: interoperability could be see at the low protocol level or a highter level, lets say at the 'service or company' level.

When today the EU talk about interoperability it's on the company level. Of course it's better if the protocol is the same or at least interoperable. But the real challenge here is to agree to collaborate.

You god a lot of response talking about protocols: matrix, xmpp or email. In my point of view that the easiest part of the interoperability, even if it already not simple.

And I was not aware that SimpleX is interoperable in any way!

I'm working on a project of service that use mainly xmpp to let us talk between xmpp, matrix and sip users ( mio.chat/en/ ;) )

MIO Chat

mio.chat
in reply to Tuta

mastodon - Link to source

Murray 🇪🇺

I keep hearing about #SimpleX but background checks on who is behind it go back to some random Russian guy based in London. Not the best recommendation for either company director or country of registration.
There's claims that it's been audited but only by one company "Trail of Bits".
Then there's SimpleX disclaimer which specifically states that it may be neither secure or safe.
Doesn't instil confidence.
#simplex
⇧