Authentication + Websockets

I have a similar question, given the reliability issues with the API, I let folks authenticate once, then give the user the power to delete all their data from a system that belongs to them if they wish to cease using it. They don’t even have to disconnect in Twitch, which some folks don’t even know exists, I think. The reason for this design was, when I was trying to check the API on a consistent basis for authentication purposes, it was coming back with failures (especially during that time period a couple of weeks ago) and I didn’t want to deal with it anymore - having my service depend upon a service that was going down every other day just wasn’t ideal.