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

How to handle spam / problematic use / bad bot behaviour? #7

Open
xurizaemon opened this issue Mar 1, 2017 · 1 comment
Open

How to handle spam / problematic use / bad bot behaviour? #7

xurizaemon opened this issue Mar 1, 2017 · 1 comment

Comments

@xurizaemon
Copy link
Owner

xurizaemon commented Mar 1, 2017

If a malicious user (or bot) interacted with @Bolts in ways that contravene the CiviCRM Code of Conduct, are annoying or harmful to individuals / community, what could we do?

  • Disable @Bolts. I am happy to do this on request of CiviCRM core team, and @Bolts could also be "locked out" by a password change by the core team. (I'm open to other requests, but I wanted this to be a concrete statement rather than something weasely like "by reasonable request", help me improve this wording?)
  • Submitted a fix over in Add ability to ignore users loafoe/hubot-matteruser#31 to make a configurable method to ignore users by name. So we have that feature now :)
@xurizaemon xurizaemon changed the title How to handle spam? How to handle spam / problematic use / bad bot behaviour? Mar 1, 2017
@xurizaemon
Copy link
Owner Author

xurizaemon commented Mar 11, 2017

I've implemented a middleware for hubot, hubot-refrain

This lets hubot stop itself from saying certain things (based on patterns stored in robot.brain). So when we have had hashtagspam appear which contained text like "🆓 GET 66 FRIENDS 🆓", we are able to instruct bolts bolts refrain add GET .* FRIENDS and bolts will no longer voice those messages originating from hubot-twitter-mention which contain the matched string.

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

No branches or pull requests

1 participant