smash-twitch-banlist
Goal
Shared twitch banlist for large smash streams.
Ban across chats for channels/events with multiple streams.
Currently set to issue 1 day timeouts. Will re-evaluate this going forward as it makes unbanning someone kind of a pain (though I'd hope that's not a common occurence with the purpose of this list). It might be worth issuing a shared timeout method to time someone out from all shared channels for a specified duration...
Live
This bot is currently deployed and live at http://twitch.tv/SmashBanlist
Commands
!join
Only available in the bot chat. Instructs the bot to join your channel. Please make the bot a mod in your channel.
!smashban [username]
Listed administrators only. Adds a username to the shared banlist.
!smashunban [username]
Listed administrators only. Removes a username from the shared banlist.
!smashadmin [username]
Listed administrators only. Adds a username to the administrator list.
!smashunadmin [username]
Listed administrators only. Removes a username from the administrator list.
!smashpermit [username]
Channel moderator/broadcaster only. Adds an exclusion to your channel for a username on the shared banlist, will also handle removing any ongoing timeouts for that user.
TODOs
- Error handling. Handling disconnects, etc.
- Server config to auto-restart/connect.
- Figure out a better way to handle username casing on twitch...
- Persist bannedUsernames and eventual admin changes.
- Persist channel list to reconnect on restart.
- Store banned usernames with timestamps, who banned, etc once there's a db in place to handle that extra info. Really don't want to increase the load on username checking.
- Add a !join command or something to allow joining your channel.
- Determine if tmi.js is more efficient at joining multiple irc channels despite having a hell of a lot more message processing.
- Decide if permabans are worth managing, seems like that would be a bit too permenant since those write to the profile. Increasing the ban timeout to some ridiculous number should be enough to ban someone for an entire event.
- Add per channel ignores allowing a channel to opt out of banning someone.
- Determine how relevant a cluster would be to distribute channels across multiple threads? Seems like the load is low enough to handle for now.
- Simple message parsing in case more commands are needed. Detecting 'admins' permit to add to the list and moderators permit to allow/revoke per channel?
- ban [username], unban [username], join [channel], leave [channel], allow [username], revoke [username] ?
- With the intent of allow/revoke being to add per channel exclusions.
- Make some kind of frontend with a listing of banned users and some instructions.
- Deploy it.
Proof of Concept log using some top channels for a chat stream, message counts were emit every 15 seconds.
Joined channel: #shroud
Joined channel: #arteezy
Joined channel: #drdisrespectlive
Joined channel: #summit1g
Joined channel: #geekandsundry
149 messages processed.
BANNED username: nactalia, channel: #summit1g
252 messages processed.
346 messages processed.
451 messages processed.
556 messages processed.
618 messages processed.
BANNED username: linsp, channel: #arteezy
702 messages processed.
776 messages processed.
BANNED username: linsp, channel: #arteezy
893 messages processed.
BANNED username: linsp, channel: #arteezy
983 messages processed.
1053 messages processed.
BANNED username: nactalia, channel: #summit1g
1112 messages processed.
1166 messages processed.
1290 messages processed.
1347 messages processed.
1412 messages processed.
1460 messages processed.
1520 messages processed.
1583 messages processed.
1640 messages processed.
1692 messages processed.
Development
Create a .env file using the params specified in .sample-env. You can get an oauth token here.