Live data from Hacker News

A Year Using Matrix and Riot

itscode.red

11–20 of 82 posts

Re: A Year Using Matrix and Riot

#12
post #4

Project 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 use Riot on a daily basis and I like the overall concept, we love federated where I communicate. So let me try to share some experiences that bugger me the most because I really hope you could imporve on those things. Imho those things are more important than UI. (form follows function, sorry guys ;D)

- Messages that can't be decrypted on only some of my devices. This for example forces me to use my phone while sitting in front of my riot desktop application. This becomes worse if ppl send me URLs. I have to forward them from my phone to my pc - using an empty channel with only me reading, having riot telling me that noone is listening :D. Im-/exporting all keys on all my devices only helps for a while and is impossible while not at home. This mostly - but not only - happens with linux.

- Searching the history doesn't work well at all. Shows zero results for a string, scrolling up proves that wrong.

- My phone doesn't stop to blink even tho I read the message on my pc.

- I really do not like electron and things relying on 100+mb google sandbox software. But well, I understand your need to use it... ;D

Re: A Year Using Matrix and Riot

#13
post #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 :)

Can't wait to see the new redesign. Hopefully it takes some hints from the host platform - it'd be great to have Riot feeling more at home on macOS!

Re: A Year Using Matrix and Riot

#14

> 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…

Probably a "quick and easy" way to fix this would be to just rely on Google's Material Design resources and tools, which I think are generally liked by most people.

This may be an alternative:

https://getmdl.io/index.html

Re: A Year Using Matrix and Riot

#15
post #4

Project 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…

> once we get past the mythical man month stage

Oh dear.

Re: A Year Using Matrix and Riot

#16
post #4

Project 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…

As others have said, thanks for everything. I am a Patreon supporter, I would highly encourage others to support Matrix/Riot as well. I have been able to transition the vast majority of my personal and professional communication to Riot.im on Android, iOS, and web. Voice, video, text, memes, all of it. I know it has its rough points, but even non technical family and friends have been able to use it, getting off of the proprietary, nonfree alternatives. Thank you very much.

Re: A Year Using Matrix and Riot

#17
post #4

Project 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 use Riot on a daily basis and I like the overall concept, we love federated where I communicate. So let me try to share some experiences that bugger me the most because I really hope you could imporve on those things. Imho those things are more important than UI. (form follows function, sorry guys ;D) - Messages that can't be decrypted on only some of my devices. This for example forces me to use my phone while sit…

> - Searching the history doesn't work well at all. Shows zero results for a string, scrolling up proves that wrong.

This is because search doesn't work at all in encrypted rooms since it's implemented server-side.

Re: A Year Using Matrix and Riot

#19
After seeing a post on HN about Matrix a few weeks ago, I decided to see about setting up a home server on the headless Ubuntu box in my closet. All in all, it was pretty painless. The one thing I couldn't figure out was the built-in audio/video calling functionality, although the Jitsi videoconferencing widget did work (once my dad I managed to find all 20 of the volume knobs throughout the OS that need to be unmuted to have both the speakers and microphone working on both ends).

Re: A Year Using Matrix and Riot

#20
post #4

Project 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…

Are chunks / hot path improvements going to help with the forward_extremities problem? https://github.com/matrix-org/synapse/issues/1760
Post reply on HN