The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Matrix-appservice-irc Alternatives
Similar projects and alternatives to matrix-appservice-irc
-
matterbridge
bridge between mattermost, IRC, gitter, xmpp, slack, discord, telegram, rocketchat, twitch, ssh-chat, zulip, whatsapp, keybase, matrix, microsoft teams, nextcloud, mumble, vk and more with REST API (mattermost not required!)
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
nimb
NIMB IRC Matrix Bridge (NIMB) is a simple client tool that bridges IRC and Matrix channels and forwards messages from one to others
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
mash-playbook
🐋 Ansible playbook which helps you host various FOSS services as Docker containers on your own server
matrix-appservice-irc reviews and mentions
-
Shutting down the Matrix bridge to Libera Chat
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....
-
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 unfortunate that it's come to this, and I can only hope that the whole "opt in with a chanmode" thing happens.
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?
-
A Quick Overview of Matrix
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.
-
We are moving past legacy Freenode to a new fork
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] 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 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...
-
Freenode has unilaterally taken over #haskell along with many other community channels
Matrix bridging to Libera is already functional in testing and should be announced soon, subscribe for news to this issue.
-
Element Matrix Services Launches Bridging for Microsoft Teams
It looks like they could be fixed as the bridge code is open source. For example here is an issue around messages being split incorrectly: https://github.com/matrix-org/matrix-appservice-irc/issues/1...
- IRC users joining a room with no ops get PL50 on Matrix side
- Netsplit can possibly cause Matrix user becoming moderator and deop by server not getting synced
- Netsplit can cause Matrix user becoming moderator and deop by server not syncing
-
A note from our sponsor - WorkOS
workos.com | 19 Apr 2024
Stats
matrix-org/matrix-appservice-irc is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of matrix-appservice-irc is TypeScript.