I hear about Matrix a lot, but I have no idea why I should use it. Can anyone explain why I should use Matrix?
It's xmpp reborn (or IRC if you're that way), with a modern feature set, so the thing you use if you want Slack but without SlackCo.
Matrix 1.0 – Are We Ready Yet?
41–50 of 208 posts
Re: Matrix 1.0 – Are We Ready Yet?
#42I hear about Matrix a lot, but I have no idea why I should use it. Can anyone explain why I should use Matrix?
- no vendor lock-in - decentralized - encrypted/private/secure - open-source It's like irc or email for private decentralized encrypted chat.
Matrix isn't really decentralized. It's federated.
Re: Matrix 1.0 – Are We Ready Yet?
#43When is the kickass Riot UI remaster that y'all showed off at Web3 coming to town?
The future is now https://medium.com/@RiotChat/the-big-1-0-68fa7c6050be
I don't want to knock the hard work the Riot developers have put into their application, but I just don't understand: why does 'modern' web design seem to require wasting so much white space? Looking at the screenshot on that blog post, the actual chat transcript is somewhere in the middle of the screen (sandwiched between giant sidebars on either side).
Compare to irssi (or any other console IRC program), which uses just about the entire width of the terminal to print chat messages.
Is this really just a side-effect of developers all having large, high-DPI monitors, making the white space look smaller to them? Because on my tiny little Chromebook, no more than 50% of the screen width is actually used to display chat messages.
Re: Matrix 1.0 – Are We Ready Yet?
#44I 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)
Re: Matrix 1.0 – Are We Ready Yet?
#45Re: Matrix 1.0 – Are We Ready Yet?
#46Earlier quoted context omitted.
To quote one of the follow up comments from the author: > If you go to matrix.org and look at the list of about a dozen or so servers: you will find that none of them actually work except the reference implementation, and maybe sometimes Construct. Even thus, the phrase "able to build" is questionable. I have spent months reverse-engineering their software and its interactions before, and after, it was at all documen…
The "good luck talking to your own federation" comment is being taken out of context. I can't find it in my history (so I assume it's been paraphrased), plus from memory I think it was the final line in an argument over how some bit of the protocol should be implemented. After failing to convince the guy that our approach was better than his proposal, I gave up with "okay, you can always do it your way, but you'll on…
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 protocol and then build e2e atop it, rather the clients should be focused on what to do with the messages after receiving them, how to display them, etc.
I say this as a daily non-Matrix.org user of Riot, the functionality of the Riot ecosystem on its own is good, but I'd be hard pressed to port my own Signal bots to Matrix, let alone build a featureful client in a performant toolkit (eg: Not Electron) for Matrix today.
There isn't a viable ecosystem outside Riot/Synapse currently, which makes it feel like Matrix is just a self-hosted Slack/Hipchat solution with just Riot as usable clients. IMO there needs to be diversity in the Matrix ecosystem just like the Fediverse has with Mastodon, Pleroma, PeerTube, PixelFed, NextCloud, Rustodon, etc all inter-operating in a sane, functional manner.
Re: Matrix 1.0 – Are We Ready Yet?
#47Earlier quoted context omitted.
The future is now https://medium.com/@RiotChat/the-big-1-0-68fa7c6050be
I don't want to knock the hard work the Riot developers have put into their application, but I just don't understand: why does 'modern' web design seem to require wasting so much white space? Looking at the screenshot on that blog post, the actual chat transcript is somewhere in the middle of the screen (sandwiched between giant sidebars on either side). Compare to irssi (or any other console IRC program), which uses…
Why would you want messages to span the entire screen?
https://ux.stackexchange.com/questions/108801/what-is-the-be...
Re: Matrix 1.0 – Are We Ready Yet?
#48Re: Matrix 1.0 – Are We Ready Yet?
#49Earlier quoted context omitted.
Matrix isn't really decentralized. It's federated.
Federation is a form of decentralization.
For example, every client could choose to run its own server to have a perfectly decentralized network. Federation is a feature that allows for greater than 1:1 mapping between clients and servers.
Re: Matrix 1.0 – Are We Ready Yet?
#50Earlier quoted context omitted.
I don't want to knock the hard work the Riot developers have put into their application, but I just don't understand: why does 'modern' web design seem to require wasting so much white space? Looking at the screenshot on that blog post, the actual chat transcript is somewhere in the middle of the screen (sandwiched between giant sidebars on either side). Compare to irssi (or any other console IRC program), which uses…
Why would you want messages to span the entire screen? https://ux.stackexchange.com/questions/108801/what-is-the-be...
Because: window managers!
http://i.imgur.com/4K0pa6m.jpg
That said...I must confess that irssi uses a non-trivial amount of margin space as well!