HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
matrix-org
matrix-appservice-irc
TypeScript2015–2025
matrix-org / matrix-appservice-irc

matrix-appservice-irc

Node.js IRC bridge for Matrix

16Distinct people
29Mentions
1Explicit recommenders
508GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Node.js IRC bridge for Matrix

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Matrix is great for bridging[0] between different chat applications. Personally I use it a lot to bridge to IRC, which is a great alternative to the older method of setting up…

siraben used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year29 dated mentions

Observed mentions: 2015-11-02 09:10:20 UTC to 2025-10-21 18:11:51 UTC.

02462015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 6 mentions; 2 submissions, 4 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC303
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC110
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC303
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC404
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC624
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC606
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

29 sources
The issue in question here is https://github.com/matrix-org/matrix-appservice-irc/issues/1... (and https://github.com/matrix-org/matrix-appservice-irc/pull/133...) which accidentally regressed due to other stability work done for Libera (specifically, keeping the IRC-side connections persistent, rather than reconnecting when the bridge starts). As a result there was an race condition edge case where users on the Matrix side could read history in the IRC channel while still connecting the Matrix users on the IRC side. This was one of the straws that broke the camel's back in terms of Libera wanting the bridge disabled. The other was the confusion over https://matrix.org/blog/2023/07/what-happened-with-the-archi....
In Shutting down the Matrix bridge to Libera chat
> Matrix is used as a decentralised bouncer for tens of thousands of users to access IRC Matrix as a whole isn't banned, only the bridge operated by Element. If anything, this could encourage more people to run their own bridges (eg. Heisenbridge). > while the bridge has certainly had problems over the years (e.g. occasional delays & a recent spate of dropped messages), As well as flood (multiline messages and edits), spam, harassment[1], leaking secret channels[2], leaking past message metadata and channel membership. [1]: https://twitter.com/AsahiLinux/status/1581103659013722112 [2]: https://github.com/matrix-org/matrix-appservice-irc/releases... > it's also improved loads too The very room used to discuss the Matrix bridge (#irc:matrix.org) has been dropping all IRC messages for at least three days, and the one to talk to Libera's staf
Read the rest
f (#libera-matrix:libera.chat) was only fixed today [EDIT: actually it's still dropping some people's messages]. The room used to discuss the Matrix spec (#spec:matrix.org) has been dropping them for over a year. After two years of message drops, there is no way for users to know their messages are being dropped without using developer tools, causing miscommunication issues to many Free Software projects. There have been, as far as I know, no work on addressing UX issues on the IRC side (primarily multiline messages, edits, and replies) in the last couple of years; except my work on MSC3968 and MSC3969 which is still awaiting initial review from Element four months after I submitted it.
In Disabling Matrix Portalling
As a user, this is miserable. Matrix is used as a decentralised bouncer for tens of thousands of users to access IRC (including me) and while the bridge has certainly had problems over the years (e.g. occasional delays & a recent spate of dropped messages), it's also improved loads too - e.g. with support for restarting the bridge without reconnecting all the IRC users (https://github.com/matrix-org/matrix-appservice-irc/issues/1...) and all the other stuff in https://github.com/matrix-org/matrix-appservice-irc/blob/dev.... By now requiring users to go and contact chanops to ask them to explicitly plumb IRC channels to Matrix, it's just going to waste time for chanops, precipitate weird cross-plumbing failures, or fail outright (given plumbing channels with more than 100 users has to be done manually to prevent abuse). It's very unfortuna
Read the rest
te that it's come to this, and I can only hope that the whole "opt in with a chanmode" thing happens, if portalling is off the table. In fact, wouldn't it have been better to just ban the bridge by default, and let chanops unban it if they want people to be able to access via Matrix, rather than encourage people into the weird world of plumbing? EDIT: clarifying that i'm not neutral on this, given i'm project lead for Matrix, and also responsible for running the Libera bridge at Element.
In Disabling Matrix Portalling
On the Matrix side, we've put a lot of effort into being good neighbours, fwiw - e.g. recently this massive refactor at https://github.com/matrix-org/matrix-appservice-irc/pull/166... to allow the matrix<->irc bridge to be restarted without reconnecting all its IRC users (the single biggest complaint we ever had about the bridge in terms of eroding usability of IRC for IRC natives). Sadly it looks like it wasn't considered sufficient, based on https://libera.chat/news/matrix-deportalling.
In A Quick Overview of Matrix
Adapting a comment I made in the wrong thread: This happened right after Freenode banned IRCCloud users following IRCCloud staff statements suggesting users to migrate off Freenode and the launch of competing bouncer services.[0] Regardless of your opinion of IRCCloud, banning all IRCCloud users right after launching a competing service and hearing criticism is not a good look. Now that most channels are dead and direct users to other networks despite staff's best efforts to quell any criticism (channel migrations+topic-renaming, banning users, etc), I guess they decided to wipe everything and start over to more easily remove any references to Libera/OFTC. In fact, it removes any every reference to anything at all. If you had a bot that directed users to the actual location of your community, you should check to make sure that it survives
Read the rest
this migration (this was probably part of the intent). If you use Matrix and have left Freenode channels, the IRC-Matrix appservice bridge might still be keeping you connected. To leave Freenode, send a "!quit" message to the Freenode bridge appservice user, @appservice-irc:matrix.org.[1][2] [0]: https://web.archive.org/web/20210612224853/https://nitter.ni... 83 [1]: https://matrix-org.github.io/matrix-appservice-irc/latest/ad... [2]: https://github.com/matrix-org/matrix-appservice-irc/wiki/Bri...
In Freenode commits suicide, is no longer a serious IRC network
This happened right after Freenode banned IRCCloud users following IRCCloud staff statements suggesting users to migrate off Freenode and the launch of competing bouncer services.[0] Regardless of your opinion of IRCCloud, banning all IRCCloud users right after launching a competing service and hearing criticism is not a good look. Now that most channels are dead and direct users to other networks despite staff's best efforts to quell any criticism (channel migrations+topic-renaming, banning users, etc), I guess they decided to wipe everything and start over to more easily remove any references to Libera/OFTC. In fact, it removes any every reference to anything at all. If you had a bot that directed users to the actual location of your community, you should check to make sure that it survives this migration (this was probably part of the
Read the rest
intent). If you use Matrix and have left Freenode channels, the IRC-Matrix appservice bridge might still be keeping you connected. To leave Freenode, send a "!quit" message to the Freenode bridge appservice user, @appservice-irc:matrix.org.[1][2] [0]: https://web.archive.org/web/20210612224853/https://nitter.ni... [1]: https://matrix-org.github.io/matrix-appservice-irc/latest/ad... [2]: https://github.com/matrix-org/matrix-appservice-irc/wiki/Bri...
In We are moving past legacy Freenode to a new fork

Showing the 15 most recent of 29 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.