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
Detecting whether the bot can kick or not by checking its channel access level is "good enough", but it doesn't cover all cases. Some networks have systems in place for granting access to KICK without granting access (e.g. Rizon's FLAGS access system). It would be great if the module could detect this, rather than simply refusing to kick if it doesn't have channel operator status.
As discussed in dgw/sopel-duel#44 there is an IRC numeric reply (482 ERR_CHANOPRIVSNEEDED) that could be caught to help with this detection, but implementing a trial-and-error system in which the bot tries to kick, and then falls back to not kicking if it's not allowed to, might be hard within the Sopel framework.
The text was updated successfully, but these errors were encountered:
Detecting whether the bot can kick or not by checking its channel access level is "good enough", but it doesn't cover all cases. Some networks have systems in place for granting access to
KICK
without granting access (e.g. Rizon's FLAGS access system). It would be great if the module could detect this, rather than simply refusing to kick if it doesn't have channel operator status.As discussed in dgw/sopel-duel#44 there is an IRC numeric reply (482
ERR_CHANOPRIVSNEEDED
) that could be caught to help with this detection, but implementing a trial-and-error system in which the bot tries to kick, and then falls back to not kicking if it's not allowed to, might be hard within the Sopel framework.The text was updated successfully, but these errors were encountered: