@cjd I note the legislation doesn't impact e2e-encrypted messages yet. Good reason to get all your contacts onto Signal.

Signal is not the ideal platform because it has a huge target on it already. Matrix would be perfect if synapse wouldn't be awful to admin. I host https://pkt.chat/ which is based on MatterFOSS (libre fork of Mattermost™), there's an e2ee plugin for that, have not tested. Deltachat is another nice one too, many options.

@cjd @freakazoid Why not XMPP? I don't like random startups inventing their own protocol instead of building on (and thus improving) existing internet standards.

@kaip @cjd XMPP is one of the dumbest protocols I've ever seen tbh. It's from the "XML is the future" era.

Follow

@freakazoid @cjd So what's wrong with it if you get over the fact that it's XML?

@kaip @cjd It's streaming XML, not just XML. It's verbose and slow to parse. And it can't handle binary data; you have to base64 encode it, which again makes it verbose and slow to parse.

@freakazoid @cjd You really think the XML parsing speed is the bottleneck in IM? If you want to send any amount of binary data where this starts to matter it's done out of band.

@kaip @cjd On a low power device RAM and CPU cycles matter. And on the server it means you need more of both per connection. It's network bound, so bottlenecks aren't usually what matter, but parsing XML at wire speed on a 10G link is certainly going to use a lot of CPU that you could be using for other things.

AFAIK no protocol before or since has used streaming XML.

1. Saying you "support XML" means you have to support all of it, and it's a very complex protocol. I believe Xerces is 10MB.
2. Streaming without any framing is just asinine, and that's why XMPP had to write their own XML parsers (which don't fully support XML anyway)

Trash heap of history.

@cjd @freakazoid 1. XMPP restricts itself to a reasonably sane subset of XML, not all of it (see RFC3920).

2. A quick look at the source code of some XMPP clients shows this is false. Not fully supporting XML would be the correct way of doing it because of (1).

Current XMPP server (and client) implementations are orders of magnitude more RAM and CPU efficient than let's say Matrix.

Saying it's better than Matrix is not exactly a shining endorsement.

@cjd @freakazoid Maybe so. What other messaging protocols do you know of that offer federated, E2E encrypted chat, A/V calls etc.?

Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!