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-...
- 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
This is because search doesn't work at all in encrypted rooms since it's implemented server-side.
The fact that you all are working so hard on performance and polish really gives me hope that soon I'll be able to pull some less technical people off of hangouts.
Matrix has an account with them, you can support them there, and 100% of your money goes to Matrix.
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.
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.
(Admittedly, Matrix's focus on global chats rather than Communities makes for a pretty complicated model/system when Communities and subflairs and subchannels need to be implemented.)
I really hope Matrix and Riot will be able to catch up with the other players in this respect, because Communities is a major reason why Discord has grown as big as it has. Powerful group administration tools encourage people to start communities on a platform, invite more people to them, and advertise those communities. It's imo a major driver of growth, and I'd like to see Matrix gain lots of market share.
It'll be hard, but best of luck, we're cheering for you.
The Librem 5 page says “partnering with Matrix” but it now sounds like that has no meaning.
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).
Presumably it's because you're decrypting a 5MB image in JS, but it seems a little bit odd that the entire browser effectively locks up as long as the image is visible.
It's not the end of the world for me, but it is fairly frustrating (the people I talk to use the Android app and don't have this problem, leading).
Keep up the great work Arathorn (and the rest of the folks working on Matrix/Riot)! I've been donating quite a bit to the Matrix project ever since you started accepting funds, and I don't regret it one bit.
I did see there was an issue opened for it on github, but can't seem to find it now.
* 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...