`Cucked` alt for promote #70

New issue

Open

opened 2024-04-08 08:43:58 -04:00 by modulatingforce · 1 comment

modulatingforce commented

2024-04-08 08:43:58 -04:00

Owner

This could turn to funny situations where BotAdmin attempts to run a BotCommand that requires Channel Elevated roles, receives an access related bot notification, then they can call cucked to promote themselves. You could even enhance it so if they call that alt specifically (cucked), it responds with a uhhh , pause for 1s, then goes through the promotion process

I want it versatile enough to do the above even if the BotAdmin passes an argument that isn't a chatter : for example, cucked wrr !!

This could also be fun for specific channel elevated users who can cuck their viewers by giving them elevated roles

At the moment, I don't think there's chatter validation anywhere in the bot that checks if the chatter exists ; I'm also not sure if this would be an expensive operation for something relatively smol so this will explore that

Promote BotCommand should have an alt : cucked . Promote should check if the given argument is an existing chatter > if the argument is not an existing chatter, and the BotCommand invoker is a BotAdmin, go through the promotion process targeting the invoker. This could turn to funny situations where BotAdmin attempts to run a BotCommand that requires Channel Elevated roles, receives an access related bot notification, then they can call `cucked` to promote themselves. You could even enhance it so if they call that alt specifically (`cucked`), it responds with a `uhhh` , pause for 1s, then goes through the promotion process I want it versatile enough to do the above even if the BotAdmin passes an argument that isn't a chatter : for example, `cucked wrr !! ` This could also be fun for specific channel elevated users who can `cuck` their viewers by giving them elevated roles At the moment, I don't think there's chatter validation anywhere in the bot that checks if the chatter exists ; I'm also not sure if this would be an expensive operation for something relatively smol so this will explore that

modulatingforce self-assigned this 2024-04-08 08:46:05 -04:00

modulatingforce added the

Requirements > Drafting

Ownership

Individual Lead

labels 2024-04-08 08:46:37 -04:00

modulatingforce added this to the Prototype 1.0 milestone 2024-04-08 08:46:51 -04:00

modulatingforce added this to the Forcebot Prototype 1.0 Push project 2024-04-08 08:46:57 -04:00

modulatingforce commented

2024-04-08 17:40:03 -04:00

Author

Owner

For each of the Requirements for promote :

Check if the Given Argument is an Existing Chatter

use https://docs.rs/twitch-irc/5.0.1/twitch_irc/validate/fn.validate_login.html
If the argument is not known login, target the invoker
- ideally, some helper fn as there are other bot commands that may target the invoker

If the call was the alt cucked specifically (rather than regular promote) ,

Respond first with uhhh , pause for 1s , then go through promotion process as normal

For each of the Requirements for `promote` : 1. Check if the Given Argument is an Existing Chatter - [ ] use https://docs.rs/twitch-irc/5.0.1/twitch_irc/validate/fn.validate_login.html - [ ] If the argument is not known login, target the invoker - [ ] ideally, some helper fn as there are other bot commands that may target the invoker 2. If the call was the alt `cucked` specifically (rather than regular `promote`) , - [ ] Respond first with `uhhh` , pause for 1s , then go through promotion process as normal

👍 1

modulatingforce added

Phase 2.0

Design > Research & Analysis

and removed

Phase 1.0

Requirements > Drafting

labels 2024-04-09 08:04:39 -04:00

modulatingforce referenced this issue

2024-04-09 09:03:44 -04:00

Cucked alt for promote #75