-
Notifications
You must be signed in to change notification settings - Fork 83
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
Add /ignore command #288
Comments
Thanks for the suggestion! I will have a look at it as soon as I find time. |
I guess this could be implemented somehow the same way as 9a31ef7. Do you have an example on how you would ignore people @marukka? Also, should that just result in the messages not being visible in frontend or also not logged? I'm sorry to say, I haven't really missed out on this feature myself, so I'm not sure when it will be implemented. Maybe @marcusramberg wants to give it a go..? |
personally I dont care. I sit in a couple channels which have bots in them which are far too active for my liking. As long as I dont have to see them i'd be happy. |
My personal preference would be to have them still logged. That way it might be possible to temporarily disable the ignore if you might feel like you're missing something pertinent, which is a feature I miss in most irc client's ignore implementations. |
I have an example. I'm on an IRC channel for a busy software project, to which some well-meaning people feed the output of the project's build bots. The channel is used for development chitchat, but it would be more easier to use for that if one could ignore everything said by a particular nick. The ignore could let through anything that would lead to a notification (e.g. "build broken; last commit by: arnt"), which I suppose might relieve some people's philosophical objections. |
I really don't like to point out the way other applications do their things, but sometimes it can help other apps to grow.
Hope this helps a bit. |
Because there are plenty of people on IRC who need to be ignored
The text was updated successfully, but these errors were encountered: