For 1-to-1 chat, XMPP seems way better suited. However, Matrix feels like a really nice IRC successor. I hope both can live in a somewhat symbiotic relationship.
A Year Using Matrix and Riot
31–40 of 82 posts
Re: A Year Using Matrix and Riot
#32Project 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…
The only thing that holds back my personal slack groups from moving to Riot is Slacks under message reactions (especially the custom ones). I did see there was an issue opened for it on github, but can't seem to find it now.
https://github.com/vector-im/riot-web/issues/1357 is the issue and we want to get it done asap, but performance and polish (as per the OP) has to take priority.
Re: A Year Using Matrix and Riot
#33Earlier quoted context omitted.
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…
Have you used any of the Qt based client? I'm asking because I'm interested in Matrix, the idea and the protocol look great but there is no way I'm using an electron app...
I use both nheko (Qt/C++), Fractal (GTK+/Rust) and Quaternion (Qt/QML) on a regular basis, and they are all very usable albeit not as mature as Riot yet. Definitely worth a go though.
Re: A Year Using Matrix and Riot
#34Project 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?
You can find me in #matrix:matrix.org or any of the public rooms about Matrix :)
Re: A Year Using Matrix and Riot
#35Project 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 any reason Dendrite hasn't gotten more attention than it has? I can understand why you wouldn't want to write a new homeserver to begin with, but I'd think you'd want to focus heavily on it once you made that decision.
Speaking of Dendrite, do you all have a general idea when it will be production-ready? I'm looking forward to being able to use it, even before it's hit full feature parity with Synapse. Just out of curiosity, how beefy is the server that the Matrix.org homeserver runs on? My VPS basically had a meltdown when I opened #matrix:matrix.org, and it wasn't even hosting the channel.
All in all, I'm pretty pleased with Matrix. It does pretty much everything I could ask, and seems very nice to develop against. The only problems I've had with it in my past few months of (admittedly, relatively light) use were related to misconfiguration on my end and Matrix.org being cripplingly overburdened.
Re: A Year Using Matrix and Riot
#36Project 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'm using Slack & Riot ... and from my point of view Slack has many of the same issues that riot has as well (performance, room switching, etc).
I agree the UX is not as intuitive as on slack, but I'm sure the get there.
One thing that I did not ever find out in the UX is how to change own presence and how to get the others presence (it's always offline).
Re: A Year Using Matrix and Riot
#37Project 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 any reason Dendrite hasn't gotten more attention than it has? I can understand why you wouldn't want to write a new homeserver to begin with, but I'd think you'd want to focus heavily on it once you made that decision. Speaking of Dendrite, do you all have a general idea when it will be production-ready? I'm looking forward to being able to use it, even before it's hit full feature parity with Synapse. Just…
The problem with Dendrite is that we've had no choice but to focus on keeping the current servers (i.e. Synapse) scaling and alive, especially the matrix.org server. The problem is compounded by the two devs who originally led Dendrite sadly leaving during the funding uncertainty we had last year.
However, we have new folks joining to work on Dendrite over the coming weeks, and we should be able to get it moving again. But it's now looking like a two-pronged attack; one to mature Synapse to being usable - and another to keep Dendrite headed in the right direction to be a good alternative (initially for AS traffic, then full CS traffic).
https://news.ycombinator.com/item?id=16940880 has a lot more info on this.
Re: A Year Using Matrix and Riot
#38Earlier quoted context omitted.
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?
We'll do a blogpost shortly to show where it's at and gather feedback :)
Re: A Year Using Matrix and Riot
#39For 1-to-1 chat, XMPP seems way better suited. However, Matrix feels like a really nice IRC successor. I hope both can live in a somewhat symbiotic relationship.
Yeah, that's their plan, I think. Bridges to other services instead of 'walled gardens' https://fosdem.org/2018/schedule/event/matrix/
Re: A Year Using Matrix and Riot
#40Earlier quoted context omitted.
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!
We don't have any plans to make a separate desktop app from Riot beyond the Electron one. Instead we're hoping that someone will write a proper native MacOS matrix client, which will be a much closer fit. https://matrix.org/docs/projects/client/matrixclient.html is the closest I know of there, but someone needs to pick it up and finish it off :)