Part of the problem is the inability to assign nicknames to contacts, so you have to remember everyone's Matrix ID.
Part of the problem is the inability to assign nicknames to contacts, so you have to remember everyone's Matrix ID.
IMO: Text chat with a few emojis and images here and there should not ever be among the things that slows your computer to a crawl.
EDIT: I'm speaking of the UI, not the network connection; the latter is sometimes slow too, but that's understandable
Native IRC clients for example have no such problem, and consume ~0% CPU at all times.
Aha, I was thinking of the mobile client, which is fine perf-wise imo. But yes, the Desktop/web client is very Slack-esque. Not in a good way.
We're still aiming for a full redesign of Riot.im to be out before end of the year, there should be things to look at at the end of the month, all crafted for the non-techy friends, so watch de the space!
And yes, the backend is not helping neither, although we've also done good progress on perf improvement there in the last months and still rolling new ones (e.g. Py3 being deployed as we speak and reducing server RAM by 3). Switching away from matrix.org can help, and agreed that a directory of public servers à la Mastodon could be interesting (although we would need to find a non-scary way to do so, lots of non-tech people would run away from it: they just want one click onboarding without having to understand what's happening behind the scenes). We've also soft launched a paid hosted offering, for 50-100 people teams who could do with their own DNS and faster servers at http://modular.im
[1] https://matrix.org/docs/projects/clients-matrix [2] https://github.com/vector-im/riot-web
Also Signal isn't federated and doesn't use the Matrix protocol.