I’m still not entirely sure what problem Sup is trying to solve. Matrix already exists. Matrix supports E2EE through the signal protocol, as well as native federation, and it bridges to almost any existing chat service. Matrix is inherently less secure, overall, than Signal, but I don’t see how Sup would fix this either – for that I’ll have to wait and see. As for using one’s fedi account to sign-in, that’s mostly just up to supporting OAuth, and not some feature that would be unique to the app.
It’s harder to maintain security due to more complexity of federated systems and Matrix does not have as much global security community looking at it as Signal has.
What I don’t like with Matrix is the load it puts on the server. It basically copies 100% of a room content to any server having one or more users registered in the room.
So if you’re on a small server, and one user decides to join a 10k+ large room, your server may collapse under the load as it tries to stay in sync with the room’s activity. This is deterrent to self-hosting or family/club/small party servers.
XMPP, on the other hand, has proven to be highly scalable, has E2EE, federation and some bridging services.
The only thing XMPP does NOT have is a single reference multiplatform client with all basic features for 2023 (1:1 chat, chat rooms, voice/video 1:1, and voice/video conference) than anyone can use without wondering if the features-set is the same as the persons you’re talking to.
And while we’re there: I’m not even sure I want a messaging account linked to any of my Fediverse accounts…
Room replication is not as big of a deal for server as it seems.
But as server admin I can say Synapse is terrible at garbage collection, the database keeps growing and growing if you don’t make your special scripts to clean it.
I’m still not entirely sure what problem Sup is trying to solve. Matrix already exists. Matrix supports E2EE through the signal protocol, as well as native federation, and it bridges to almost any existing chat service. Matrix is inherently less secure, overall, than Signal, but I don’t see how Sup would fix this either – for that I’ll have to wait and see. As for using one’s fedi account to sign-in, that’s mostly just up to supporting OAuth, and not some feature that would be unique to the app.
How is matrix less secure? If you don’t mind me asking.
It’s harder to maintain security due to more complexity of federated systems and Matrix does not have as much global security community looking at it as Signal has.
What I don’t like with Matrix is the load it puts on the server. It basically copies 100% of a room content to any server having one or more users registered in the room.
So if you’re on a small server, and one user decides to join a 10k+ large room, your server may collapse under the load as it tries to stay in sync with the room’s activity. This is deterrent to self-hosting or family/club/small party servers.
XMPP, on the other hand, has proven to be highly scalable, has E2EE, federation and some bridging services.
The only thing XMPP does NOT have is a single reference multiplatform client with all basic features for 2023 (1:1 chat, chat rooms, voice/video 1:1, and voice/video conference) than anyone can use without wondering if the features-set is the same as the persons you’re talking to.
And while we’re there: I’m not even sure I want a messaging account linked to any of my Fediverse accounts…
Room replication is not as big of a deal for server as it seems. But as server admin I can say Synapse is terrible at garbage collection, the database keeps growing and growing if you don’t make your special scripts to clean it.