Talk:Arch IRC channels

From ArchWiki
Jump to navigation Jump to search


Perhaps we should investigate a migration to matrix. We can bridge with irc so the move would be 100% transparent to existing users.

Aleccoder (talk) 18:23, 10 November 2019 (UTC)

This has been discussed multiple times and no consensus could be reached but Matrix already runs a freenode bridge:
But there would be no "migration" in either case, irc will stay.
Namarrgon (talk) 18:55, 10 November 2019 (UTC)
Even if irc will stay for some users, I think there should be a noticeable mention of a Matrix channel. I added the Matrix article to related, but for some reason it was removed as unrelated by Alad. Then maybe just create a link to this article from main page? Because IRC channels are discoverable, while Matrix are not. I did not even know about existence of that channel, before I knew that Matrix exists and then intentionally searched if the Arch Linux channel exists.
Ashark (talk) 13:37, 6 May 2021 (UTC)
There is no official Arch Linux matrix channel, so this is why it was edited out as irrelevant. This is also why User:Alad removed the mentions of the telegram bridges.
--- NetSysFire (talk) 14:05, 6 May 2021 (UTC)
Arch runs its own Matrix homeserver with IRC bridges for team members, but I don't think you're talking about this. I think the best way to make the options more discoverable would be to improve Matrix, List of applications/Internet#IRC clients and List of applications/Internet#Matrix clients somehow. — Lahwaacz (talk) 10:42, 9 May 2021 (UTC)

Channels list ordered alphabetically

I just edited a bit the channels lists to apply alphabetic order of the channels name. While translating to Portuguese, I felt that the international channels list being order by language name would not help much the translationg, as the translated language names 1) would make no sense in alphabetic order as they can have another leading letter (e.g. Czech -> Tcheco, in Portuguese), or 2) would require reordering the translated language names which would make harder to keep the translated synchronized with the original page.

I also reordered the #archlinux-proaudio channel in the "Other channels" section, for the same channel alphabetic order.
-- Josephgbr (talk) 10:04, 24 November 2020 (UTC)

Libera IRC

Warning: IRC users are required to identify with services before they can take part in official Arch Linux IRC channels, like #archlinux. The entirety of this Libera IRC article section should be read.
Comment: Already stated in the instructions; under “Register with NickServ”. Mpan (talk) 12:50, 20 June 2021 (UTC)
As of 2021-05-24, Arch Linux has moved its channels to See for details about why.
Comment: No need for historical notes. Mpan (talk) 12:50, 20 June 2021 (UTC)

Because is a new network, some guidance can help users migrate and/or get onto Libera securely.

Comment: I’d remove this part, going straight to the instructions. Mpan (talk) 12:50, 20 June 2021 (UTC)

Connect to Libera

See for upstream documentation on connecting to Libera's IRC network.

Register with NickServ

Primary Arch Linux channels, like #archlinux, require a user of the IRC network to be registered and identified in order to participate in conversation. In order to register and identify your nickname with the Libera network, one can follow their upstream guide:

Cloak Yourself

Comment: I would remove this whole section. Obscuring IP addresses is not the primary function of cloaks. It’s more of a side effect. They may be used to improve privacy in addition to other methods, but the improvement is minimal. At the same time I observe that the level of protection is overestimated by users, leading to false sense of security. Mpan (talk) 12:50, 20 June 2021 (UTC)

When using IRC, a cloak can be used to obfuscate network addresses used to connect to a network from other users on the network. This can help a lot to reduce the possibility of DDOS and attacks in general.

This is done by giving a user a "fake" host, in the form of user/<nickname>. When a cloaked user is /whois'd, the following information is gained: nickname!~username@user/nickname.

Gaining a cloak is highly recommended for all users of Libera.
Comment: By whom? Mpan (talk) 12:50, 20 June 2021 (UTC)

To gain a cloak, make sure you are first logged into services by identifying yourself with NickServ and perform the following actions on

Comment: #libera-cloak is temporary: a mechanism to offload work from the staff during the migration. I expect that after the transitional period it will come back to normal Freenode routine: asking for a cloak, providing a good reason. Mpan (talk) 12:50, 20 June 2021 (UTC)
/join #libera-cloak
/msg #libera-cloak !cloakme

After sending the !cloakme command, you will be kicked from the channel and receive a user cloak which persists with your NickServ account. This can be verified by performing a /whois <irc_nickname> on yourself.

SASL Authentication

For further protection, users can configure SASL Authentication for their IRC clients, which performs the identification step at connection.
Comment: SASL is not providing protection. It provides automation. In particular allows logging in before +r channels are autojoined. Mpan (talk) 12:50, 20 June 2021 (UTC)
This removes any time where your host may be exposed in the case a user has gained a cloak. Please see for upstream documentation on configuring SASL on Libera for various common IRC clients.

Kevr (talk) 06:36, 26 May 2021 (UTC)

+1 from me for adding this to the article. -- Svito (talk) 11:31, 20 June 2021 (UTC)
Alternatively just this tip would be enough:
  • To hide your network address from the other users (can be seen through /WHOIS username command) get a virtual hostname "cloak" by joining #libera-cloak and typing !cloakme. You will be kicked from the channel and receive a user/username cloak which persists with your NickServ account.
  • For further protection, configure SASL Authentication for your IRC client, which performs the identification step at connection. This removes any time where your host may be exposed in the case a user has gained a cloak. See upstream documentation on configuring SASL on Libera for various common IRC clients.
-- Svito (talk) 12:18, 20 June 2021 (UTC)
Arch IRC channels#Registration already mentions SASL for avoiding race condition of joining channels before login in a Note. Perhaps we can merge those bits somehow. -- Svito (talk) 12:29, 20 June 2021 (UTC)
The CertFP section in the irssi article requires an update; I have been notified, that it is no longer true. In particular a SHA512 FP is needed on Libera, not a SHA1. I couldn’t fix that myself, since I’m not using CertFP and therefore can’t **reliably** test.(Already done) --Mpan (talk) 12:52, 20 June 2021 (UTC)
As discussed here and on #archlinux-offtopic (most points are already mentioned in draft comments by mpan) I no longer think this should be merged. Cloaks are more useful to identify you as you with a bot (Phrik#Identify with hostname). -- Svito (talk) 13:43, 20 June 2021 (UTC)