The discussion revolves around issues with Twitch embeds in Discourse, specifically their small size (300x150 vs. YouTube’s 480x270) and auto-play behavior. AdamCapriola argues that Twitch embeds should not auto-play and should match YouTube’s display size. chapel explains that this is due to Twitch’s metadata limitations, requiring a custom onebox parser. codinghorror agrees, stating it’s a Twitch issue. DanielMarquard shares a link to a related topic, while codinghorror questions if Twitch oneboxes auto-play. eviltrout notes that Twitch no longer embeds videos, and codinghorror suggests native handling. eviltrout mentions adding improved Twitch embedding support in the onebox gem. Falco shares a Twitch clip link, highlighting the ongoing discussion.
YouTube videos don’t auto-play, so I don’t think Twitch embeds should either. Also, the display is small compared to YouTube (300x150 vs. 480x270). A consistent width for embeds would be cool.
Oh and the preview display for Twitch channels is kind of odd (it shows the channel’s profile image but only the embed is shown once the post is published).
Unfortunately this is what Twitch proves in their meta data that Discourse uses to embed.
It would require creating a custom Twitch Onebox parser which would do it’s own logic. That or similar to LazyYT, create a LazyTwitch which would make a better preview and click to play without actually loading the Twitch embed.