Access freenode using Matrix clients

Fedora Linux 34 Background with freenode and Matrix logos

Matrix (also written [matrix]) is an open source project and a communication protocol. The protocol standard is open and it is free to use or implement. Matrix is being recognized as a modern successor to the older Internet Relay Chat (IRC) protocol. Mozilla, KDE, FOSDEM and GNOME are among several large projects that have started using chat clients and servers that operate over the Matrix protocol. Members of the Fedora project have discussed whether or not the community should switch to using the Matrix protocol.

The Matrix project has implemented an IRC bridge to enable communication between IRC networks (for example, freenode) and Matrix homeservers. This article is a guide on how to register, identify and join freenode channels from a Matrix client via the Matrix IRC bridge.

Check out Beginner’s guide to IRC for more information about IRC.


You need to set everything up before you register a nick. A nick is a username.

Install a client

Before you use the IRC bridge, you need to install a Matrix client. This guide will use Element. Other Matrix clients are available.

First, install the Matrix client Element from Flathub on your PC. Alternatively, browse to to run the Element client directly in your browser.

Next, click Create Account to register a new account on (a homeserver hosted by the Matrix project).

Create rooms

For the IRC bridge, you need to create rooms with the required users.

First, click the ➕ (plus) button next to People on the left side in Element and type in the field to create a new room with the user.

Second, create another new room with

Register a nick at freenode

If you have already registered a nick at freenode, skip the remainder of this section.

Registering a nickname is optional, but strongly recommended. Many freenode channels require a registered nickname to join.

First, open the room with appservice-irc and enter the following:

!nick <your_nick>

Substitute <your_nick> with the username you want to use. If the nick is already taken, NickServ will send you the following message:

This nickname is registered. Please choose a different nickname, or identify via /msg NickServ identify <password>.

If you receive the above message, use another nick.

Second, open the room with NickServ and enter the following:

REGISTER <your_password> <>

You will receive a verification email from freenode. The email will contain a verification command similar to the following:

/msg NickServ VERIFY REGISTER <your_nick> <verification_code>

Ignore /msg NickServ at the start of the command. Enter the remainder of the command in the room with NickServ. Be quick! You will have 24 hours to verify before the code expires.

Identify your nick at freenode

If you just registered a new nick using the procedure in the previous section, then you should already be identified. If you are already identified, skip the remainder of this section.

First, open the room with and enter the following:

!nick <your_nick>

Next, open the room with and enter the following:

IDENTIFY <your_nick> <your_password>

Join a freenode channel

To join a freenode channel, press the ➕ (plus) button next to Rooms on the left side in Element and type #freenode_#<your_channel> Substitute <your_channel> with the freenode channel you want to join. For example, to join the #fedora channel, use For a list of Fedora Project IRC channels, see Communicating_and_getting_help — IRC_for_interactive_community_support.

Further reading

Addendum – June 1st, 2021

Due to the recent announcement, many projects have switched to Libera Chat, including Fedora.

To join Libera Chat channels, make the following substitutions when using this guide:

  • →
  • →
  • appservice-irc → appservice
  • freenode_#<your_channel> → #<your_channel>
  • →
FAQs and Guides


  1. SigmaSquadrons

    GSmall typo on the third topic: Creat rooms.

  2. Kyra

    I love that Fedora is doing this migration, but this creates such a high barrier to non-technical users seeking live support. I hope eventually users can just get access through matrix without the confusing IRC config.

    • We’re working on getting a Fedora homeserver set up. This will make it easier for more parts of the project to use Matrix natively. Whether or not the user support channel (#fedora) moves from IRC-based to Matrix-based remains to be seen

    • I agree! I think we’ll eventually move to a matrix-first approach, which will make this all much easier.

      • Ryan

        Jumping through hoops with NickServ and the like just remind me how painful IRC can often be, especially for new users. I am for a matrix-first approach 110%

  3. wheelie207

    I’d rather not use a browser to access the IRC as I use to use the oldr irc chat clients that had it’s own window with the use of a browser.

  4. wheelie207

    I meant without the use of a browser.

  5. Dustin

    I 100% support a move to Matrix!

  6. I wouldn’t be against a move to Matrix as long as an IRC bridge remains functional; a Matrix migration isn’t worth forcing IRC users to pull out a second client. I’ve written up my concerns about Matrix in the past:

    It mostly boils down to Matrix’s complexity and lack of implementation diversity. Yes, it’s an open protocol, but it’s not as open a platform as IRC.

    I’d prefer sticking to the current setup (Freenode with the Freenode bridge) but skip the registration requirement for Matrix users, if possible. This might require writing a new bot that checks for nick hostnames.

    I think most of IRC’s issues are client-side; the protocol itself is fine for public rooms (the lack of e2ee isn’t a concern if a room is public).

Comments are Closed

The opinions expressed on this website are those of each author, not of the author's employer or of Red Hat. Fedora Magazine aspires to publish all content under a Creative Commons license but may not be able to do so in all cases. You are responsible for ensuring that you have the necessary permission to reuse any work on this site. The Fedora logo is a trademark of Red Hat, Inc. Terms and Conditions