If two people send a www command, for example, they will run together until the first one ends. In which case, the second www will end earlier than it is supposed to, because the reset of the first www will resest the controller input of the next one.

when a disconnect happens (presumably), the controller will still run in a bugged state where it does not receive any further input from Twitch despite sending PONG responses. When this happens, we need to find a way to restart the connection.

Some possible fixes:

• reconnect to twitch after some delay all the time to guarantee reconnection eventually
• reconnect on socket disconnect (sometimes this happens and the program closes)
• reconnect on twitch disconnect somehow (this appears as sending a PONG to Twitch and not getting any responses for an extended period)