How to use Matrix

on 2022-12-29

As I've gotten more into FOSS, I've noticed a lot of FOSS projects, like KDE, use Matrix protocol.

A protocol that lets you use any client you wish to chat with each other. Basically, it's IRC but with more features.

And I'm into that! So I decided to move my Aks_Dev community from Discord to Matrix. Just to support the project in general but also I do not want my community to be tied to one client. In fact I've been using Matrix-Discord bridge for a while, but it is not the optimal way to chat, IMO. Some things just drop out, like replies from Discord side. It works but.. It would be better if everyone was just on the Matrix side.

On top of the bridge being Very Good but Not Optimal, Discord being proprietary platform can easily follow the path of Twitter. Who knows when Discord decides to add cryptocurrencies or other meaningless crap? Who knows where your data is going to? And if you want to use different client, Discord just can easily ban you because it's their walled garden and you're the prisoner of convenience.


Enough of ranting, here's how you get most of Da Matrix, in my holy opinion:

Create account to one of the instances

Try to avoid if you can. Meanwhile it is the biggest instance, that is also its downside. If runs out of money to host the server, then it's bye-bye for all the accounts using it.

I think one good alternative to is Mozilla's instance:

Edit: I have learned that Mozilla's instance is hosted by the Element Matrix Services, so it's not as decentralized as I hoped. If that doesn't matter to you, you can just use it, but if it does, read on.

If you are savvy enough, just self-host your own instance. But if you know how to do that, you probably are not reading this post anyhow.

You can also get your own instance through these hosting services:

Make sure the instance you join is not ACL-banned (Access Control List) by This will make it harder for you to federate with other servers.

Here is also one list I found from searching:

Pick one with rules and privacy policy, then make sure you read the rules well. Check that there is nothing weird about the instance.

Edit: The host of the contacted me and told me to create a report for them if the list has a weird instance.

But I don't want to think too much of this!

Then, go for either or Mozilla's instance.

Use Element to set up things

Meanwhile Element is not my daily-drive client, I always create the new account using it and set it up wit it. It is made by people who also work with Matrix protocol, so it usually has all the features needed to get you going.

So, use Element to create your account and set it up. I think of Element as the "control panel" of my account, and not the actual chat client I use.

Pick your client

This is not necessary if you like Element and it has all you need! But I've noticed many new Matrix users have problems using Element since it has a lot of going on!

So many buttons and widgets. So many things cluttering around. And no custom emoji support (as of writing this)!

This is why I recommend getting another client. My favorite newcomer-friendly client is definitely Cinny!

It has custom emoji support, it has less noisy interface, it works with E2EE and basically, it works well as a basic chat client.

There is also desktop version of Cinny, but it's a bit hidden for some reason:

You can find more clients from here if you're curious: Official client list

However, what I would do is the following:

Element as control panel and back-up client. Cinny as the main client I use daily, either on desktop or web-browser.

E2EE verification stuff

E2EE = end-to-end encryption

This is where the UX is not very good yet... Basically, when logging in to Cinny, you'll see a popup that says something about "verify your client/account."

This means that the encryption key, that is used to encrypt your conversations, will be shared between these clients. So when you verify a device, the client with the key will send it to the other client. In this case it would be from Element to Cinny.

The usual verification dance is following:

  1. You have set up your account in Element, but want to now try a new client.
  2. You open the new client in another window, for example Cinny, and log in. Keep Element open!
  3. Cinny or Element warns you that your account is unverified, since there is a new client connected to it.
  4. You click the shiny Verify button in either client (I usually always start the verification process from Element)
  5. You accept the verification process in the other client.
  6. You have to check if some emoji's match and say Yes in both clients.
  7. This dance now should be done.

I think there are better ways to do this, like QR codes or something, but it's clearly still in WIP to see what kind of verification method will be the one that'll stick.

If you do not use chats with E2EE enabled, the verification process is not necessary. But I do it anyhow because the popups are annoying, lol.

My community does not use encrypted chats, because bots do not work with those.

Android client

I don't know anything about iOS, but on Android, Fluffychat is what I use. Works well for my usage. Android version of Element is also fine, but it doesn't have custom emoji support. See the client list linked above for more.

And yes, you'll have to do the verification dance here as well. Again I recommend starting it from Element on desktop.

Voice and Video

These are still WIP. I think only Element and Nheko clients have voice chat working, and I'm not sure if anything else but Element has video chat working.

For these, you're probably best served with Discord. If you want FOSS voice-chatting, check out Mumble. It's the old reliable and I've used it for years.

For video chats, I do not know at all what would work. Leave comment if you do, though!

Quick Summary for the TLDR peeps

  1. Use Element to create an account to or Mozilla's instance.
  2. Set up your account inside Element.
  3. Download Cinny for your desktop and/or use it from your browser.
  4. Use Cinny as your chat client, Element as your "control panel" client.
  5. Get some mobile client if you wish.
  6. Set up E2EE by verifying the other clients from Element.

What about XMPP and IRC? Why Matrix?

I actually love both XMPP and IRC. I've used both and they still are very reliable ways to chat.

However, most folk I chat with seem to use Matrix, and if you run your own homeserver like I do, you can easily bridge to both XMPP and IRC if needed. That's why I've chosen to stick with Matrix in this case.

Personally I don't really care about the protocol, I just want something that is not proprietary and the communities I am in use. Matrix seems to bridge with anything so for me it made most sense.

The best thing we can do, however, is not to fight over protocols but make these open protocols easily to talk to each other, so we can choose anything we wish.

To have any chance against proprietary stuff, we must not fight among ourselves, but work together. We are all in this together, after all!


Aaaand that's all. I hope this "guide" helped a bit.

Matrix is still very young and figuring things out. It's complicated and I believe they're adding features a bit too fast, so things are not always very fleshed out.

But for basic text chatting it works fine for me, and is not proprietary.

So if you want a community to join in with your Matrix account, hop on to Aks_Dev chat!

Aks_Dev Matrix Community

You can ask me questions about Matrix in there or just comment to this post. :)