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.

Sign up for GitHub

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

Jump to bottom

Ban users by nick #51

Closed
archangelic opened this issue Feb 13, 2019 · 3 comments
Closed

Ban users by nick #51

archangelic opened this issue Feb 13, 2019 · 3 comments
Assignees
@archangelic
Labels
core issues related to core pinhook functionality such as plugin reloading, internal commands enhancement additional features irc issues related directly to IRC
Projects
pinhook

Comments

@archangelic
Copy link
Owner

There should be an internal command that ops can add a user by nick that cannot interact with a bot (commands and messages to listeners should be ignored)

Should be paired with an unban command.
@archangelic archangelic added enhancement additional features irc issues related directly to IRC core issues related to core pinhook functionality such as plugin reloading, internal commands labels Feb 13, 2019
@archangelic archangelic self-assigned this Feb 13, 2019
@archangelic archangelic added this to To-do in pinhook via automation Feb 13, 2019
@RussellChamp
Copy link
Contributor

I'm guessing this would mean some sort of data persistence? how would you like to do that? however it is done, either prepend it with the bot nick or allow users to specify the file name or something...

@archangelic
Copy link
Owner Author

Ah yeah, none of the data is persistent in pinhook. All the config stuff i'm doing is reading before initializing the bot, so this will have to be tied into it.

@archangelic archangelic mentioned this issue Feb 22, 2019
Open
@archangelic
Copy link
Owner Author

So, would having the bot initialize and keep a sqlite database with this information be a good route?

@archangelic archangelic moved this from To-do to Priority in pinhook Sep 30, 2019
pinhook automation moved this from Priority to Done Oct 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@archangelic archangelic

Labels
core issues related to core pinhook functionality such as plugin reloading, internal commands enhancement additional features irc issues related directly to IRC
Projects
pinhook
Status: Done
pinhook
  
Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@RussellChamp @archangelic