Determine Rate Limit Approach

[clarkio]

I'm opening up this issue to provide a forum for discussion on how we can best implement a way to isolate and/or prevent abuse of the chat command.

So far some suggestions I've noticed from the community are as follows:

• limit based on time (e.g. a viewer can only highlight once every X seconds/minutes)
• limit based on role (e.g. only mods or vips can highlight)
• temporary ban/timeouts for abusers (e.g. no highlights for X seconds/minutes/banned)

Please feel free to add more suggestions, expand on one or share which approach seems best to you.

[danielhe4rt]

I think the first thing u need to do is check the command spam (i did't have time to read your code yet) and set some rules to timeout and ban.
idk if this options can be setted by the user, but if not, there is a great idea

[Apidcloud]

You could also set a limit on the vs code client side (in addition to another one on twitch). That is, only X suggestions per minute (independent from the number of people suggesting)—sort of a funnel.
After that threshold show a notification saying that there are Y on the queue (maybe listed per viewer) where you can choose to accept or not.

That said, I think it's really important to have safety checks on both sides. Say you have 50 viewers or more and each one highlights a line. I think it's way too much, and thus suggesting doing it at vs code side too.

[ConnBB]

• Allow mods to ban/timeout viewers.
  (-bloodconn)