-
Notifications
You must be signed in to change notification settings - Fork 181
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
implement banforwards #1238
Comments
my suggestion would be that we store the forward channel in |
That makes sense. We'd want to make sure that you can't forward in loops. Maybe you only get one redirect? |
sounds good. perhaps we could change the big regex to be |
I think it's not necessarily going to be straightforward to determine which clause was matched, just from the matched substring. (Although if you can see a way to do it, that would certainly be interesting.) When I benchmarked re. syntax, note that |
Might it be cleaner to have one single all-purpose overflow channel? (Covering user limit, invite-only, registered-only, and all bans.) |
yes that's usually cmode |
as for |
an example of how this concept works, from charybdis:
/mode #chan +b *!*@badhost$##fix-your-connection
will forward anyone matching the mask to the given channel - mask and channel being delimited by
$
.i'd be very happy if the format could remain the same, but it wouldn't be the end of the world if it can't.
The text was updated successfully, but these errors were encountered: