Hi George, yeah I pretty much have what you described working already. The server creates a new connection for each client that wants to log into their account and connect to Twitch. I’ll be implementing the rate limiting as well. Currently, the really vital stuff is all handled by the server - the clients are unable to perform any business logic as you say. As for scaling, I’ll be doing a limited network test soon, starting small, and increasing the number of allowed connections (and server resources) as needed.
The clients just ask the server to do things for them, including send messages to Twitch - at which point the server will either agree and tell them the result, or tell them they don’t have permission, based on a variety of factors, including account permissions and soon rate limiting. The clients update accordingly to the server’s response.
I’m just concerned about the “one IP = lots of connected accounts” question the most.