this post was submitted on 16 Jun 2024
23 points (89.7% liked)

Matrix

3281 readers
2 users here now

An open network for secure, decentralized communication

founded 4 years ago
MODERATORS
k_o_t@lemmy.ml
23
Does anyone know when can we expect to communicate with whatsapp or facebook messenger users on element? (sh.itjust.works)
submitted 4 months ago* (last edited 4 months ago) by hostops@sh.itjust.works to c/matrix@lemmy.ml
10 comments fedilink hide all child comments
 

Edit: Question based on DMA: element.io/blog/the-eu-digital-markets-act-is-here/

you are viewing a single comment's thread
view the rest of the comments
[–] testman@lemmy.ml 9 points 4 months ago (1 children)

As far as I know, the Signal protocol was chosen to be the intermediary layer between the existing platforms. Matrix protocol was a candidate, but was not chosen.

Still, if you wish to use a bridge between Matrix and some other platform, then you can either set one up yourself or try to find a Matrix server that already has such bridge set up. https://matrix.org/ecosystem/bridges/

[–] BarHocker@discuss.tchncs.de 4 points 4 months ago (1 children)

Do you have any articles or publications about that decision being made?

[–] testman@lemmy.ml 4 points 4 months ago (1 children)
[–] azdle@news.idlestate.org 3 points 4 months ago

I am still interested to know the details of how they came to this decision. Why Signal instead of Matrix.

AFAIK, signal doesn't federate, There is no "signal server-to-server" protocol. When people say "The Signal Protocol", they are talking about a cryptographic protocol, not a network protocol.

As for why they wouldn't use Matrix, I would assume it's just too heavy of a protocol for the scale they operate at. IIRC, Matrix isn't just a chat protocol. It's a multi-peer cryptographic state synchronization protocol. Chat is (was?) just the first "easy" application they were going to apply it to. (Now I'm curious if they still have plans for that at some point.) They've been making great strides in improving the efficiency, at least in the client-server API (I haven't been paying attention to the server-server API at all), but it's still going to be a heck of a lot more compute heavy than whatever custom API they're providing.