The fact that was ever made permanent honestly hurts Twitch’s reliability in my mind significantly. I work with a company that helps non-profits and charities fundraise and one of the things we did was integrate Twitch into our platform for live streams. Now we are getting the PSoD more and more often even when internally testing in our QA environment (fully qualified domain, SSL, etc.). At this point I’m beginning to question if our idea of running a Twitch based gaming fundraiser to showcase the integration is even a good idea, let alone a case we want to push for our users. We have partners waiting in the wings, but they are expecting us to solve this issue and if there isn’t a solution then it’s not Twitch they or the end users will go to, it will be us. What should we tell them? “This isn’t our problem, it’s Twitch, they want you to go complain individually on their ‘UserVoice’ page to gauge how many people this affects and upsets.”? That seems like a great way to open the door for people to leave. That doesn’t convert them on our side, nor does it convert them to Twitch. Our user base is highly mixed, some will know Twitch, most likely won’t.
What are we supposed to do? Are we just caught in the crossfire as Twitch tries to monetize as much as possible and left to hope you can get something figured out that doesn’t completely kill the user experience?