KDE To Support Matrix Decentralized Instant Messaging

[Mavman]

Question: Is matrix decentralized or distributed?

I know it advertises itself as decentralized but there is this weird blur line between the two and the more I read about it, the less I seem to understand the diferences.

I get the feeling that there are a few projects that, while they are "distributed" they are using the "decentralized" word for marketing motives

Can anyone bring some light to the subject, please?

[Damnshock]

Question: Is matrix decentralized or distributed?

I know it advertises itself as decentralized but there is this weird blur line between the two and the more I read about it, the less I seem to understand the diferences.

I get the feeling that there are a few projects that, while they are "distributed" they are using the "decentralized" word for marketing motives

Can anyone bring some light to the subject, please?

It's decentralized and federated (or not, depending on your liking and, afaik, you can even choose whether to federate or not by room)

[Damnshock]

Yeah, IM is hard - because for it to be effective you need not only like and use it, but it also needs to be somewhat popular to have friends, colleagues, etc. jump on the bandwagon. The only application I've been able to find that foots that bill is Telegram. It has a native client for just about every known platform - including Linux - and the Linux client is GPLv3.

I'll definitely look into matrix, but I'm not optimistic that it will reach any type of critical mass which would make it a true competitor in the already crowded IM space. The best solution for the Linux community right now for a mainstream IM client is Telegram.

P.S. Just did a quick look into matrix and found that it's desktop client for Linux is electron based - which means it's basically just a chromium web page. The Telegram client is Qt based - which again points to Telegram's commitment to provide a native client for every platform. Apparently, Matrix not so much.

There several attemps to implement some client with Qt, for example:

Quaternion

Nheko

I particulary see a good future in Quaternion as the base library is evolving solidly and can be used by other projects

[gbcox]

There several attemps to implement some client with Qt, for example:

Quaternion

Nheko

I particulary see a good future in Quaternion as the base library is evolving solidly and can be used by other projects

Thanks! I'll take a look.

[Mavman]

It's decentralized and federated (or not, depending on your liking and, afaik, you can even choose whether to federate or not by room)

But, from my understanding, being distributed would be better for us, users, that like privacy and security, wouldn't it?

[Vistaus]

Can you video call using different apps on different networks? Matrix is Skype, Viber, Discord, Slack, Email killer. You basically have something like email (@user:server.com) with a lot of modern features. It should be called E-mail 2.0.

It's not the only one in its kind, though. Delta Chat is a more popular direct competitor to this.

[Vistaus]

IRC is obviously too old compared to the competition. I know... you can do a lot with IRC if you know the commands and everything and it's a protocol that will always be there, and it's 130% open and everything. But it's basically just a text messaging app and modern apps can do a LOT more than just that.

As for XMPP, I had high hopes for this protocol... but in the end it's unusable. There is no client (to my knowledge) that does it well. I'm talking about basic text messaging of course, but also voice chat, video chat, screen sharing, file sharing, extensibility, etc..

All this is available in Matrix and its client, Riot. As paupav said, it really feels like e-mail 2.0.

How is Matrix different from e.g. Delta Chat?

[Nocifer]

But, from my understanding, being distributed would be better for us, users, that like privacy and security, wouldn't it?

It's decentralized, because it does need servers to operate, but it's also distributed in the sense that the metadata is shared only between the participating users/homeservers, which can be completely independent from the "central" Matrix network (which in fact does not really exist, in the same way that a "central" email network does not exist either, it's simply autonomous servers optionally talking to each other).

How is Matrix different from e.g. Delta Chat?

For one, it allows for voice and video calls (granted, the latter with the use of an extra software component). And also it allows for other chat protocols to communicate with itself and each other via bridges, so it allows for existing IM users to still use their IM network of choice (granted, pretty much everyone these days has an email address, so this point can be considered moot). And also it's a proper chat protocol with all the bells and whistles that come with one, and not just a glorified mailing list. Other than that, though, I can't say this Delta Chat sounds bad, quite the contrary. But despite what you've said about it being "more popular", this is the first time I've ever heard of it.

[zanny]

What I don't understand is the purpose of Matrix: It seems to me that instead of fixing/improving existing IMs, they're reinventing the wheel.
Existing IMs: IRC and XMPP. Both have mature servers and clients, have vetted protocols (In RFCs!).
So: Why Matrix?

IRC is an ASCII based arbitrary text wire protocol.
XMPP is XML soup.
Matrix is HTTP and JSON based, so everything is http methods passing around json objects.

As someone who has contributed to Konversation, KDE Telepathy, Pidgin, and various Matrix projects... nobody wants to try to work in either the IRC or XMPP protocols. They are giant dumpsterfire messes, be it because they are too nebulous and cross-client support is atrocious, or because they are too bureaucratic in how so many extension proposals turned out. At least when we have something as clean as http json apis like Matrix now.

You can spec out the matrix client API with most JSON libraries in a weekend by comparison. The only hard parts to support are WebRTC and the Matrix OLM because they both require third party libraries be included and integrated with your GUI.

[bug77]

IRC is an ASCII based arbitrary text wire protocol.
XMPP is XML soup.
Matrix is HTTP and JSON based, so everything is http methods passing around json objects.

As someone who has contributed to Konversation, KDE Telepathy, Pidgin, and various Matrix projects... nobody wants to try to work in either the IRC or XMPP protocols. They are giant dumpsterfire messes, be it because they are too nebulous and cross-client support is atrocious, or because they are too bureaucratic in how so many extension proposals turned out. At least when we have something as clean as http json apis like Matrix now.

You can spec out the matrix client API with most JSON libraries in a weekend by comparison. The only hard parts to support are WebRTC and the Matrix OLM because they both require third party libraries be included and integrated with your GUI.

Tbh, there's no technical reason XMPP messages cannot be directly translated to JSON/BSON/protobuf. And the long lived HTTP connection can be turned into an web socket. Thus the protocol could be more modern and efficient.
Of course, proper governance and stewardship of XEPs would still be required.