-
Notifications
You must be signed in to change notification settings - Fork 197
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
Allow UBAN ADDing realnames/gecos #1724
Comments
This seems like a "moderate on the other side of the bridge" problem? As in, if an operator or a bot has the ability to issue these bans on the Ergo side, they would be able to do it more effectively on the Matrix side? |
Unlike RELAYMSG, the bridge spawns ghost users on IRC side kind of pretending to be a bouncer and the bridge may not be always be ran by the same people as Ergo. This is the case in our network that is migrating to Ergo and also Libera.Chat. |
I'm thinking it would be interesting to develop a vendor extension that would allow "puppeting" bridges (like matrix-appservice-irc and go-discord-irc) to send an identifier for the user during registration, which Ergo could then hash into a unique cloak (using the account cloaking algorithm). The bridge would send something like: |
So go-discord-irc uses |
From discussion, we think go-discord-irc's algorithm: doesn't work with Ergo because it produces ipv6 addresses that are all in the same /64, so in the default Ergo configuration they receive an identical cloak. |
@Half-Shot thoughts? |
Biboumi (a xmpp to irc gateway) does implement webirc and thus allows xmpp server level bans without banning the gateway itself. At least on the more federated xmpp network that is usually sufficient to block abuse. |
I think |
I hit this again recently and was also asking on |
matrix-appservice-irc generally doesn't allow users to change realnames/gecos so thus the only way for operator to ban abusive users/homeservers is to ban by realname/gecos.
The text was updated successfully, but these errors were encountered: