matrix-appservice-irc
                                
                                
                                
                                    matrix-appservice-irc copied to clipboard
                            
                            
                            
                        Node.js IRC bridge for Matrix
The IPv6 counter is global to the whole bridge, so multiple networks never re-use the same IP. While this could be inferred to as by design, there doesn't really seem...
I'm trying to join #\:libera.chat but it keeps failing. I keep getting errors on Matrix side like `There was an error joining.` or `Failed to make_join via any server`. On...
We found a couple of those recently, as rooms with seemingly broken bridging. They'd show up in the database as rooms with invisible trailing whitespace: ``` > select * from...
For `#emacs:libera.chat`, the channel mode contains `+c`. > `c` colour filter | Strip colour and formatting codes from channel messages. > > -- https://libera.chat/guides/channelmodes Currently, user does not have an...
**Describe the bug** Some IRC users prefer to not be signed in when they're not on IRC, so they do not use bouncers. However, Matrix sometimes still shows the presence...
When a Matrix user is connected to a channel which is bridged to IRC, limitations on message length should be communicated to the Matrix client, which should enforce them. I...
Hello, and sorry if this is the wrong place to ask for this. I was directed here in #libera-matrix:libera.chat, and told that if I want to bridge a big room...
This is probably a duplicate of one of the existing desync issues, but I managed to reproduce it deterministically: 1. join an empty `#testchan:libera.chat` from Matrix (it's currently broken from...
It's an extension (https://ircv3.net/specs/extensions/labeled-response) supported by various clients in order to show responses relations to the original message.
**Describe the bug** I receive the (somewhat infamous?) "Failed to unlink room. Check the logs for details." message upon using the `!unlink` command. I think that the logs it refers...