10000 Spam Filtering · Issue #35 · scubot/scubot · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Spam Filtering #35

< 8000 div class="gh-header-actions mt-0 mb-3 mb-md-2 ml-1 flex-md-order-1 flex-shrink-0 d-flex flex-items-center gap-1">
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
Open
the-emerald opened this issue Nov 13, 2017 · 6 comments
Open

Spam Filtering #35

the-emerald opened this issue Nov 13, 2017 · 6 comments
Assignees
@QuickRecon @the-emerald
Labels
enhancement
Milestone
Production fixes

Comments

@the-emerald
Copy link
Member

Some ideas based off of existing spam filter rules, given a spam constant s:

  • s per message decreases with time between messages
  • s per message increases with length of message
  • s with multiplier per message if the message is a repeat
  • s with multiplier per message if user is new

And a whole lot more rules, but finding the balance between too many rules and being too simple could prove challenging.

The offending user could be muted, isolated to a channel, kicked, etc if their value of s exceeds a threshold.
@the-emerald the-emerald added this to the First deployment milestone Nov 13, 2017
@the-emerald
Copy link
Member Author

Another idea would be a 'raid alarm'. Can be activated by an admin, channels and new users joining are locked down for a while.

@QuickRecon
Copy link
Collaborator

Perhaps we need a bot admin role, to keep things simple

@the-emerald
Copy link
Member Author

I'm thinking about something like deco with a folder:

spamfilter
|___ spam.py # Where the logic happens (e.g. conditions above)
|___ constants.py # Where the constants are held (e.g. multipliers)
|___ raid.py # Raid alarm logic

I'm going to write some really rough code (pass galore) in the next day or so to get a better sense of how to tackle the problem!

@QuickRecon
Copy link
Collaborator

Spam Filter

@sinetwo
Copy link
sinetwo commented Nov 22, 2017 •
edited
Loading

Notification to @ moderators and @ admin would be really useful - i.e. if someone exceeds an s value and an action is invoked (e.g. mute or move user) then those @ roles should ideally be notified in a PM so they're aware.

@the-emerald
Copy link
Member Author

Awesome! Will add that to the list of features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@QuickRecon QuickRecon

@the-emerald the-emerald

Labels
enhancement
Projects
None yet
Milestone
Production fixes
Development

No branches or pull requests
3 participants
@QuickRecon @the-emerald @sinetwo
0