Thanks Barry for being so useful, what you wrote makes total sense, I assumed you needed auth to listen to broadcast, now I realise it didn’t make too much sense 
I am still experiencing the issue, backend works flawlessly with a 204 respone, the dev rig on the other hand doesn’t seem to care about my brodcasted messages.
Opening the console and refreshing the view I get this error:
twitch-ext.min.js:22 Uncaught (in promise) ERR_BADAUTH
value @ twitch-ext.min.js:22
value @ twitch-ext.min.js:1
value @ twitch-ext.min.js:22
I still get those hanged connections, I tried with firefox and safari, and tried it with a vpn just in case my provider does something dodgy, no change at all, they still stay on 101. I even looked at http://websocketstest.com/ and it seems to work fine, what could be the issue here?
Thanks for your patience and understanding 
This is my full js code:
const twitch = window.Twitch.ext;
let isAuthed = false;
const logToRig = (topic, loggable = '') => twitch.rig.log(topic, loggable);
twitch.onContext(context => logToRig('onContext', context));
twitch.onError(context => logToRig('onError', context));
twitch.onAuthorized(function (auth) {
logToRig('onAuthorized', auth);
logToRig('token', auth.token);
isAuthed = true;
});
twitch.listen(
'broadcast',
(target, contentType, message) => {
if (isAuthed) {
logToRig('Broadcast', { target, contentType, message });
} else {
console.log('Ignored');
}
}
);