Hey Barry, Team,
The problem is that you are bound and listening to all messages and capturing a undocumented/unsupported event that you shouldn’t be handling in the first place.
From our perspective, we have discovered the source of extra load and interrupts. So
please try to see it from our side as well. Just because we ignore them doesn’t mean they are not happening and eating up performance and causing interruption to screenshare display.
Is there a documented way to destroy the embed so the messages will stop?
Something like TwitchEmbed.remove() (similar to jquery… FYI we are not using jquery)
I’ve tried to point out that all three of these message types appear to be unnecessarily frequent and repetitive. Hopefully that is helpful feedback to the team.