Live data from Hacker News

Matrix 1.0 – Are We Ready Yet?

matrix.org

91–100 of 208 posts

Re: Matrix 1.0 – Are We Ready Yet?

#91

I made a seq2seq chatbot with Matrix/Riot, the python-api implementation ( https://github.com/matrix-org/matrix-python-sdk ) and https://github.com/tensorlayer/seq2seq-chatbot : Here it is: https://www.youtube.com/watch?v=rCggOcKZn-c (There's a fun interaction at 25:52)

That triple nested if is horrible though…

Re: Matrix 1.0 – Are We Ready Yet?

#92
post #35

I sincerely hope someone took the Telegram client code and add Matrix protocol to it. Really, Telegram client is open source and the app is more usable than any other bloatware on the market.

Agreed, the Telegram desktop client is super fast.

EDIT: Someone seems to already have done this:

https://matrix.org/docs/projects/client/nheko.html

Re: Matrix 1.0 – Are We Ready Yet?

#93

Earlier quoted context omitted.

It'd be great if there were usable non-Riot clients that fully supported end to end cryptography. At this point Signal has better alternative clients in Pyre.chat and Signal-Weechat than Matrix has, as the existing alternative clients are almost all MVPs missing major features like e2e. The lack of a simple, common library is a real sticking point. Each client & bot shouldn't have to implement the baseline network pr…

So, other clients with fully working E2E encryption include: Seaglass, Weechat, Pattle and nheko (although it needs to implement attachments, but they is easy). The weechat and nheko implementations are independent implementations (ie not the same as the Riot ones). We are starting work this week on closing the E2E gap for all the rest.

I don't think Pattle has e2ee support, from what I can see on my phone. While it is built on the Matrix Android SDK which has e2ee support, the app itself doesn't seem to use that support yet.

Re: Matrix 1.0 – Are We Ready Yet?

#94

I'm not very much into chat apps and protocols, but isn't it possible to just revive XMPP? Ten years ago we used Adium and Pidgin, and federated chat seemed like a solved problem. I understand XMPP with its extensions and use of XML fragments might be complex, but it sounds like matrix or another new protocol isn't easier. In a way, those willing to invest time into F/OSS chat apps have done the best they could with…

Why are people so attached to XMPP? There was no entity preventing XMPP from thriving, if the community really wanted XMPP, we would have had XMPP everywhere. But honestly, as someone who ran and tried to use XMPP for many years, the entire protocol was an unmaintained divided mess. And the XEPs didn't help, they felt like hacky workarounds to keep an old protocol up-to-date with the modern needs. Matrix feels very c…

I have very same impression. XMPP is basing on XML where parsing is order of magniture more complex than JSON. In lot of ways very similar to SOAP mess where you could not comunicate across different software because each of them supportet different set of SOAP extensions and good luck with communicating with web client.

Re: Matrix 1.0 – Are We Ready Yet?

#95
post #31

The home page gives no clue as to what "Matrix" is. It seems to be yet another "federation" system. Is this worth any attention?

It's the standard problem of software designed by software engineers: they have a problem turning off their geek-brain to see how a potential user views it.

Matrix folks:

* if a teenager cannot understand what it is in 10 seconds of looking at it or if a teenager does not download the client after understanding what it is your product is hopelessly broken

* if a 30 year old cannot understand what it is in 20 seconds or upon understanding does not immediately install that software, your product is hopelessly broken

* if a 50 year who has facebook just looks at your website funny, then your product is hopelessly broken.

Re: Matrix 1.0 – Are We Ready Yet?

#96

Earlier quoted context omitted.

Why are people so attached to XMPP? There was no entity preventing XMPP from thriving, if the community really wanted XMPP, we would have had XMPP everywhere. But honestly, as someone who ran and tried to use XMPP for many years, the entire protocol was an unmaintained divided mess. And the XEPs didn't help, they felt like hacky workarounds to keep an old protocol up-to-date with the modern needs. Matrix feels very c…

I have very same impression. XMPP is basing on XML where parsing is order of magniture more complex than JSON. In lot of ways very similar to SOAP mess where you could not comunicate across different software because each of them supportet different set of SOAP extensions and good luck with communicating with web client.

> XML where parsing is order of magniture more complex than JSON

You're supposed to use an off-the-shelf XML/JSON parser, not write it yourself.

Re: Matrix 1.0 – Are We Ready Yet?

#97

I'm not very much into chat apps and protocols, but isn't it possible to just revive XMPP? Ten years ago we used Adium and Pidgin, and federated chat seemed like a solved problem. I understand XMPP with its extensions and use of XML fragments might be complex, but it sounds like matrix or another new protocol isn't easier. In a way, those willing to invest time into F/OSS chat apps have done the best they could with…

I am completely on your side. Matrix did improve upon the state of XMPP in 2012. But XMPP improved too and therefore the problems we had 2012 are not relevant anymore today.

There is just one big problem with XMPP nowadays: Very few people are interested in XMPP as everybody wants to learn the new shit aka Matrix. And actually, that is the one thing I blame the Matrix devs for. Instead of improving an existing open IETF standard they decided to invent something new and split the community.

Technologically, Matrix is neither better nor worse than XMPP, as far as I can tell, but splitting the community wasn't such a brilliant idea.

Re: Matrix 1.0 – Are We Ready Yet?

#98

I'm not very much into chat apps and protocols, but isn't it possible to just revive XMPP? Ten years ago we used Adium and Pidgin, and federated chat seemed like a solved problem. I understand XMPP with its extensions and use of XML fragments might be complex, but it sounds like matrix or another new protocol isn't easier. In a way, those willing to invest time into F/OSS chat apps have done the best they could with…

The problem of XMPP is just lack of good clients on some platforms, most notably for iOS. For Android there is an excellent Conversations.im client [0] that I've successfully use with my non-technical family and friends. (There is also Quicksy [1] that uses phone numbers for onboarding but it's XMPP all the way down). Conversations doesn't use a lot of battery (anecdata but it's 1% on my phone) and just works.

[0]: https://conversations.im/

[1]: https://quicksy.im/

As for servers ejabberd is successfully used from small deployments to big MMORPGs. The team is extremely focused on performance and from what they say XML isn't actually a big performance problem. Prosody, another server, is in my opinion also high quality, even though it's developed in free time (AFAIK).

The "myriad of extensions" is mostly solved problem due to Compliance Suites and automated testers [2] (think SSLLabs) that people use to get their servers in shape.

[2]: https://compliance.conversations.im/

For the record I've used Matrix for work too and it's not bad, the clients are decent (I've used web client), but it's not a revolution especially if one's contacts can use Conversations, that, in my opinion, is just very good.

Re: Matrix 1.0 – Are We Ready Yet?

#99

I'm not very much into chat apps and protocols, but isn't it possible to just revive XMPP? Ten years ago we used Adium and Pidgin, and federated chat seemed like a solved problem. I understand XMPP with its extensions and use of XML fragments might be complex, but it sounds like matrix or another new protocol isn't easier. In a way, those willing to invest time into F/OSS chat apps have done the best they could with…

Plenty of us are still working on XMPP, and there are thousands of XMPP servers and many more users on the network. It's true that since the original Jabber project began in 1999 there was a vision of giving users freedom of software and service, yet that vision is still nowhere near reality in 2019. But we are still an active community and still work towards that vision. XMPP is not dead. Unfortunately Pidgin and Ad…

For those searching a very simple to use XMPP client:

Quicksy.im: https://play.google.com/store/apps/details?id=im.quicksy.cli...

It is a fork (same developers) of the popular Conversations client, which does not bother you with provider selection and such kind of technical decisions. If you just want to try XMPP or invite someone, it is probably the easiest way to start with.

Re: Matrix 1.0 – Are We Ready Yet?

#100

I'm not very much into chat apps and protocols, but isn't it possible to just revive XMPP? Ten years ago we used Adium and Pidgin, and federated chat seemed like a solved problem. I understand XMPP with its extensions and use of XML fragments might be complex, but it sounds like matrix or another new protocol isn't easier. In a way, those willing to invest time into F/OSS chat apps have done the best they could with…

> isn't it possible to just revive XMPP? Please no. XMPP has adapted over time to support various chat and instant messaging features that we today take for granted. These adaptions come in the form of Extensions[1]. A year ago I spent about two hours with a geek friend to configure something that resembles what we get from any other instant messenger today. That's not acceptable to the outside world. Meanwhile, Matr…

> Funny thing, Matrix is still struggling (like every other federated network) to explain the concept of federation.

Are there any data on how federated is Matrix? I mean number of users on different servers.

From my experience most of people are on matrix.org server and even if they run their own homeservers the identity server is still vector.im.

Post reply on HN