A Year Using Matrix and Riot
itscode.red
A Year Using Matrix and Riot
1–10 of 82 posts
Re: A Year Using Matrix and Riot
#2I would've liked a better segregation of how it was a year ago and how it is now, along with some kind of bullet list showing the salient points that the author wants to highlight.
I've tried Riot briefly, and am very much interested to see such a decentralized solution becoming mature. I really can't wait for it to become something that can be "sold" to people who aren't into technology but care about the user experience and ease of use.
Re: A Year Using Matrix and Riot
#3> This has improved a lot since a year ago but there still needs to be a massive change in the UI design to make it comparable to the competition.
I agree whole-heartedly with this. I am not entirely sure who decided on Riot's garish green UI filled with circles and non-standard UI controls and wildly variable padding/spacing and communities bar that takes up space even when not joined to any communities, but it looks a mess.
If you look at Slack, Microsoft Teams etc, they are consistent, they are clean and they look like they have been designed by professionals. Riot doesn't - yet - and I can quite understand that putting people off, given that there aren't many other Matrix clients for the average user.
Re: A Year Using Matrix and Riot
#4Project lead for Matrix here. This is a pretty accurate post, and in terms of the negative points we are painfully aware that UX on Riot (and performance on Synapse) still has a way to go. The current stuff we have in flight to fix this are:
* Lazy-load all room members rather than push them proactively to clients. This should improve initial sync times and subsequent RAM usage by anywhere from 3x to 20x depending on how active your account is.
* Cross-sign E2E devices when you log in so nobody ever has to verify them again. This should kill the constant device verification (and key sharing) warnings.
* Refresh the whole UI/UX of Riot. We have an ex-Canonical/Ubuntu pro-designer working on a complete facelift of Riot/Web, coming in the next few months.
* Perf improvements across the board on Riot/Web - particularly optimising React when switching rooms, and switching from Draft to Slate in order to speed up and stabilise the message composer.
* Algorithmic improvements to Synapse to speed up the hottest paths (shifting from O(N) to roughly O(1) with the size of the room) - https://matrix.org/_matrix/media/v1/download/jki.re/ubNfLtrm...
* Algorithmic improvements to Synapse to avoid fragmentation of rooms by partitioning the DAG into 'chunks', avoiding stale/dead/orphaned chunks from contributing to the fragmentation of the overall room - https://docs.google.com/document/d/1E0cmEeMDwcQarFYxpZ0b9aoQ...
On the minus side, we've been badly slowed down by constant firefighting keeping the Matrix.org homeserver operational despite massive growth, as well having to do a lot of preparation for GDPR compliance - see https://matrix.org/blog/2018/05/08/gdpr-compliance-in-matrix....
On the plus side, we have a lot of new people joining during May to work fulltime on Synapse, Dendrite and Riot/Web - which once we get past the mythical man month stage should make a huge huge difference.
Fun times...
Re: A Year Using Matrix and Riot
#5> This has improved a lot since a year ago but there still needs to be a massive change in the UI design to make it comparable to the competition. I agree whole-heartedly with this. I am not entirely sure who decided on Riot's garish green UI filled with circles and non-standard UI controls and wildly variable padding/spacing and communities bar that takes up space even when not joined to any communities, but it look…
You're always welcome to change the garish green in settings, and likewise hide the communities bar (although we expect communities to be used more and more in future, just as they are in Slack and Discord etc).
Meanwhile, the upcoming redesign pretty much removes the green and the circles anyway :)
Re: A Year Using Matrix and Riot
#6One thing I discovered when introducing other people to Riot.im and that even confused myself was the sign-up procedure. You think you are signing up but instead you are trying to sign in.
Other than that I am happy with Riot.im.
Re: A Year Using Matrix and Riot
#7Project lead for Matrix here. This is a pretty accurate post, and in terms of the negative points we are painfully aware that UX on Riot (and performance on Synapse) still has a way to go. The current stuff we have in flight to fix this are: * Lazy-load all room members rather than push them proactively to clients. This should improve initial sync times and subsequent RAM usage by anywhere from 3x to 20x depending on…
Thanks for the work you're doing here! I want to commend you on how well and consistently you communicate the priorities and progress of this project. Between the This Week in Matrix[0] blog posts, the Matrix Live chats for the Patreon patrons, and your presence here and on matrix/irc, I'm impressed at your organization and the results you've managed to produce!
I'm happily using Riot with my wife and our 60+ year old parents, as well as with my peers, and we all really like it. This project is really shaping up to be a gem of the open-source community, and I'm excited to see it grow!
[0]https://matrix.org/blog/2018/05/04/this-week-in-matrix-2018-...
Re: A Year Using Matrix and Riot
#8Project lead for Matrix here. This is a pretty accurate post, and in terms of the negative points we are painfully aware that UX on Riot (and performance on Synapse) still has a way to go. The current stuff we have in flight to fix this are: * Lazy-load all room members rather than push them proactively to clients. This should improve initial sync times and subsequent RAM usage by anywhere from 3x to 20x depending on…
I'd like to help as well. Is there a way to contact you?
Re: A Year Using Matrix and Riot
#9Project lead for Matrix here. This is a pretty accurate post, and in terms of the negative points we are painfully aware that UX on Riot (and performance on Synapse) still has a way to go. The current stuff we have in flight to fix this are: * Lazy-load all room members rather than push them proactively to clients. This should improve initial sync times and subsequent RAM usage by anywhere from 3x to 20x depending on…
Is there a bunch of work going on from the team there in preparation for the Purism Librem 5, or is that mostly their efforts that happen to rely on your tech?
Re: A Year Using Matrix and Riot
#10> This has improved a lot since a year ago but there still needs to be a massive change in the UI design to make it comparable to the competition. I agree whole-heartedly with this. I am not entirely sure who decided on Riot's garish green UI filled with circles and non-standard UI controls and wildly variable padding/spacing and communities bar that takes up space even when not joined to any communities, but it look…
You're always welcome to change the garish green in settings, and likewise hide the communities bar (although we expect communities to be used more and more in future, just as they are in Slack and Discord etc). Meanwhile, the upcoming redesign pretty much removes the green and the circles anyway :)
Where can one sneak a peak of the redesign?