You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2021. It is now read-only.
eir currently messages the user who sets a ban on a channel requesting:
Please comment on the following: ban[XXXXX] <mask> was set on <#channel> by <user> on <date> and had an expiry date of <datestamp>.
It would be great if eir waited an $appropriate amount of time after a ban was set (say 30 seconds or so) prior to requesting a ban reason be set.
eir should use this time to wait for, look for, or detect a kick in the same channel as the ban was set in, who's kicked user hostmask also matches the previous set ban hostmask.
If this condition is met, eir should set the existing ban entry reason to the kick reason if it is set. If no reason is set, eir should do what it normally does, message the user that set the ban.
This saves manual effort / duplication / accidental entry mangling
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
eir currently messages the user who sets a ban on a channel requesting:
It would be great if eir waited an $appropriate amount of time after a ban was set (say 30 seconds or so) prior to requesting a ban reason be set.
eir should use this time to wait for, look for, or detect a kick in the same channel as the ban was set in, who's kicked user hostmask also matches the previous set ban hostmask.
If this condition is met, eir should set the existing ban entry reason to the kick reason if it is set. If no reason is set, eir should do what it normally does, message the user that set the ban.
This saves manual effort / duplication / accidental entry mangling
The text was updated successfully, but these errors were encountered: