thanks for such prompt replys, appreciate it 
Yes I meant that the “setMuted = false” command only works if the player is initialized as muted. Not about chromes autoplay policy. If you initialze normally, the player trys to play with audio, gets muted and cannot be unmuted with js. I thought it might be helpful to others to add to twitch API documentation.
Hmm interesting, so you deploy to a server every time you test a change?
The strictness of the parent policy also means you can’t embed node apps on your website as iframes - for instance i have a subdomain club.fractalfantasy.net for my node app and a main domain fractalfantasy.net where I host all projects/apps as iframes. We have a big release tomorrow and I had to kill our main site and redirect to the subdomain because twitch won’t load in the iframe (even if the subdomain and domain are specified). This may seem like a niche use case, but ive seen other developers struggling with the parent policy and other APIs like youtube dont have this limitation.
I understand the reasoning for the parent policy but was just thinking perhaps it doesnt need to be this strict?