Currently the limits for the normal account type allow to check 12.5% strings per minute compared to just sending those via chat to test if they pass automod restrictions. This drops to 2.08% per hour. (This drops to 2.5%/min and 0.42%/hour if the ability to have VIPs is unlocked)

The current rate limit types also seem to assume that larger streams are affiliate and or partners which is not necessarily true as there's game publishers who hold game release streams with easily 50+ viewers while not being partner/affiliate and channels who have decent amounts of viewers but do not stream often enough to reach partner/affiliate. Both of which are having to deal with unrealisticaly low limits based on the account type compared to actual activity.

These limits are also limit 3rd party tools as it is not feasible to preventively check messages sent by automated systems against a basic level of automod rather than having to build an own database to limit the amount of messages that could be breaking the Community Guidelines. Lets take a chat bot as example, on creation/modification of a custom command the bot could check if the provided response passes a basic level of automod and subsequently allow or deny the action based the result. This would lower the amount of potentially Community Guideline breaking messages as public general use chatbots like Nightbot/Moobot are and will continue to be used to try spreading malicious messages. While being at at scales where it is impossible to moderated every created/modified response in a timely manner (if at all).

Considering the above I suggest:
- The account specific rate limits to be removed as they're based on a general but not always correct assumption of viewer/msg count per account type and severely limit the exceptions.
- The Limit per hour to be removed and Limit per minute to be raised to 200 per minute to align with what is currently possible via chat in an 1 account situation.
- (Optionally) create a form where larger applications can request ratelimit increased when consistantly getting (close) to the ratelimits.

This all in an attempt to create Twitch a safer platform while also reducing the amount of effort developers have to go through to be able to achieve the same.