Saturday, August 10, 2019

Using RainRatBot for Moderation - Summary

Since the list of moderation features was spread across multiple blog posts, I'm making a summary post of what features are available and how they are activated.

Just by adding @RainRatBot to your group:

  • Remove known-bad user ids (Requires "Ban users" permission)
  • Remove known-bad display names (like "DEX airdrop") (Requires "Ban users" permission)
  • Remove latest spammers that write "hi", then edit their message to contain a link. (Requires "Ban users" and "Delete messages" permission)
  • Identify fursuits in photos if confidence above 90% (Can be suppressed per group, PM me for assistance)

Requires configuration:

If you're expecting one of the ones that requires configuration to be active in your group, PM me for assistance.

Tuesday, June 25, 2019

Using RainRatBot for Moderation - Bot Defense - Keywords Update

When I first wrote the bot defense, bots joined groups and it was a long time before they actually said anything. Back then, I said that if that changed, I would update the bot defense to keep up. Now, bots typically send spam as soon as they join.

To start updating my bot defense, I started with my keyword list. I added four public lists of spam pitches, subject lines, and domains. They were mostly oriented to email spam, but it's a starting point.

Now, if a suspected bot joins and posts text that matches something on the keyword list during the watch period, they get banned, and RainRatBot automatically deletes the spam.

I highly recommended users that use the anti-bot measures in an SFW group also give the keyword list a try. I've made dozens of additions and deletions based on feedback from group owners. In a typical SFW group, I'd expect about one false positive per year. You can ask that the keyword list be notification-only to give it a try.

Wednesday, May 29, 2019

Using RainRatBot for Moderation - Global Ban List

This is obsolete; the Global Ban List is now called the Community Ban List.


If you've been using RainRatBot for defense against rogue bots, as described in https://rainratbot.blogspot.com/2018/08/using-rainratbot-for-moderation-bot_28.html you've seen it remove the rogue bot from your group after a short time. Up until now, even if it already removed the rogue bot from another group, it's treated it as a completely new user when it joins your group; there hasn't been a Global list of rogue users, until now.

Any user on this list will immediately be banned as soon as they enter any participating group. This is the list for rogue bots, and the worst of the worst(real users who are a hazard to any group they join).

Users will be checked against Global Ban List as they join. Existing users will not be affected.


Anyone can request a global ban, however, only authorized users can approve additions.

/rrbglobalban [user id] [reason]
Adds user id to list but does not activate the ban. (ie. /rrbglobalban 123456789 spambot)
You must fill out the reason. Any user in any group may use this. The requester's user id is logged.

/rrbglobalunban [user id]
Authorized users only. Removes user id from global ban list.

/sendglobalban
Authorized users only. Reply with the proposed global ban list.

/reloadglobalban
Authorized users only. Until this command is used, changes made with /rrbglobalban, and /rrbglobalunban will not be active.


There is also an Appeals function in case of a mistake.

/rrbrequestglobalunban [reason]
Any user may use; id will be recorded. Only brings to attention of authorized users. Does not change the ban list.

/sendglobalunbanrequest
Authorized users only. View the unban requests.