search

kubernetes-sigs / slack-infra

Tooling for kubernetes.slack.com
Apache License 2.0
90 stars 36 forks source link

List of words/phrases to auto-moderate #27

Closed jeefy closed 3 years ago

jeefy commented 4 years ago

If we can tie into the firehose, it might be a good idea to watch for a list of bad words or phrases and auto-moderate them (tombstone, delete, message user)

Maybe in time we could do more but I think this is a good start.

Thoughts?

Katharine commented 4 years ago

This is somewhat difficult to do — the bot would have to join every channel (which it certainly could do).

There’s also the problem of what words are bad words, how we deal with evading the filters, etc. I imagine there are literal books on why this is a hard problem.

jeefy commented 4 years ago

I agree on the problem being hard to solve 100%, but I'm thinking of solving it 65%.

fejta-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

fejta-bot commented 4 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten

fejta-bot commented 4 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close

k8s-ci-robot commented 4 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/slack-infra/issues/27#issuecomment-612185714): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Send feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
nikhita commented 4 years ago

/reopen

k8s-ci-robot commented 4 years ago

@nikhita: Reopened this issue.

In response to [this](https://github.com/kubernetes-sigs/slack-infra/issues/27#issuecomment-674814432): >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
cpanato commented 4 years ago

@Katharine @jeefy @nikhita I did a small POC in my own slack and w can use the events API to get messages posted in the channels and then we can take actions, like moderate and let the admin know and do whatever we want.

It only receives public channels messages and not listen to DM/private.

We if this sounds what we want i can work in the code to create the app and then we need to set up the k8s slack to send the events.

ref: https://api.slack.com/events/message.channels

cpanato commented 4 years ago

if we want to move forward we need to define what we want to do if a word/phrase is found.

nikhita commented 4 years ago

@cpanato -- we decided that we'd want a bot DM the person who wrote the message containing problematic phrases and not publicly call out folks.

I believe @phumberdroz is already working on this.

Some context in this slack thread - https://kubernetes.slack.com/archives/C4M06S5HS/p1588103132093300

cpanato commented 4 years ago

thanks @nikhita

fejta-bot commented 4 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close

k8s-ci-robot commented 4 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/slack-infra/issues/27#issuecomment-694153514): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Send feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
nikhita commented 3 years ago

/reopen /remove-lifecycle rotten

k8s-ci-robot commented 3 years ago

@nikhita: Reopened this issue.

In response to [this](https://github.com/kubernetes-sigs/slack-infra/issues/27#issuecomment-774855647): >/reopen >/remove-lifecycle rotten Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.