Hacker News Reader

Comment by t0bia_s | Hacker News Reader

Your hosting, your rules.

Most of my family use my brother's Matrix server, but it's the Element app that makes it appealing to us all. Client side scanning could be enforced in the app, regardless of the server's protections.

However there is a whole ecosystem of clients, and they can't all be back doored. You are also free with write your own client, and many do (which is why we have so many in the first place).

Protocols, not platforms, people!

But if in a group only one person uses a compromised client, all communication is compromised, isn't it?

Potentially, yes. But that's where Signal's protocol helps. It includes plausible deniability.

Therefore even if your chat log is leaked by one member, it isn't possible to probe person A sent the message. If person B was the leaker, anyone that person B has ever communicated with on Signal could have sent the message appearing to be from person A.

Not in the Matrix ecosystem. The protocol is so brittle there's only one real server and one real client, probably intentional, since the designers of the protocol make money from that server and that client.

There’s three servers I know and like 10 clients.

Not sure when you last looked at the landscape.

Servers: Synapse, dendrite, conduit

Clients: (just off the top of my head)

Element, fluffychat, cinny, neochat, cyphon, nheko, schildichat

Apart from Synapse, server implementations are stuck in permanent beta.

Clients outside mobile OSes are not interesting if you are considering Signal replacements. On mobile, you have element and maybe fluffychat.

It is still a messaging thingie that lacks a decent server implementation, and lacks a good client app.

Current EU politics motivate some to develop more. Where is oppression, there is reaction.

I love Matrix but they do have a bit of a monoculture problem which I hope will get better when the protocol stabilizes. As long as they document their standards we should be fine. Their big commercialization push could turn out to be problematic in the long run, but we have to give them the benefit of the doubt and see.

If you want all the voip bits in place and all the latest features, you have to run a specific combination of synapse, sliding-proxy and element as the client. The xmpp ecosystem has similar problems but it gives a bit more leeway with various combinations of servers and clients that work well.

Matrix has more focus on IRC-like rooms, has a lot more features for that purpose and is much nicer to use than any conference xmpp extension.

https://matrix.org/ecosystem/clients/

https://matrix.org/ecosystem/servers/

The designers of matrix decided to shift more of the burden of the protocol to the server so that clients would be easier to implement. Therefore there are few servers and many clients. e2ee makes the client more complicated, that's why not all clients support e2ee

There are also several element forks. I would imagine there would be a fork without scanning if the main element app was doing scanning.

An their law.

Not on iOS.

Your choice

Reply on news.ycombinator.com