-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue] No method exists to ban Matrix users harassing the bridged IRC<->Matrix channels #1815
Comments
Is this on OFTC? Ban them by their unique IPv6 address. |
Yes, it is on OFTC. |
The issue is not really clear. After talking in the chat the actual issue are bans and K-Lines not getting bridged to Matrix under certains circumstances. As a result some OFTC channels have lots of spam on their Matrix portals, but the IRC side doesn't get any of the spam. |
True K-Lines should be actioned as users should be kicked from any room they are unable to get a IRC connection in, unless the room admin has opted to de-op the bridge and is unable to perform the kicks (which is in itself a problem). Are there example rooms we can take a look at? |
X-Lines should be considered as well. We are currently observing appservice-irc catching up for hours due to a wave of account spam joining over the bridge. The bridge is now trying to reconnect all these users after a restart and takes hours to iterate over all these hosts.
|
I have looked thru the documentation and unable to find any current methods that exist to ban Matrix users harassing the bridged IRC<->Matrix channels that are maintained by Matrix.org listed here https://matrix-org.github.io/matrix-appservice-irc/latest/bridged_networks
The text was updated successfully, but these errors were encountered: