Skip to content
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

Detect kicking ability more intelligently than channel access #44

Open
dgw opened this issue Apr 9, 2017 · 1 comment
Open

Detect kicking ability more intelligently than channel access #44

dgw opened this issue Apr 9, 2017 · 1 comment
Assignees

Comments

@dgw
Copy link
Owner

dgw commented Apr 9, 2017

With the ability of some networks to let channel owners grant kicking privileges without giving channel access (e.g. +r in Rizon's FLAGS access system), detecting whether the bot can kick simply by checking its channel access level is naïve and limiting.

The most likely way to make it smarter is to try kicking and then catch the 482 numeric ERR_CHANOPRIVSNEEDED if the bot is not allowed to use KICK, then optionally cache that status for that channel.

Not actually sure of the best way to do this sort of try/catch structure that depends on the response from the IRCd. Sopel isn't really designed to alter its behavior while handling one event based on an event that comes in afterward…

@dgw
Copy link
Owner Author

dgw commented Apr 10, 2017

Note to future self: Share implementation with dgw/sopel-BombBot#34 if you can make this happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant