That timing issue of clips on twitch is interesting.
Here is an example clip with the described issue: https://www.twitch.tv/patty/clip/ThoughtfulMoldyGarlicWutFace-BeJzyXTm1kfwGKPK
You will notice that the video starts at different times (compare the on-screen timer in the bottom left of the stream) on Firefox and Chrome/Chromium.
Preface: Video codecs usually don't just save "full" frames for every frame, instead they save changes only and only every now and then have a "keyframe" or "I" frame that is a full frame, upon which consecutive frames base their changes on (these are called "B" and "P" frames).
There is nothing that dictates that an MPEG container must start with a keyframe from what I could tell.
But realistically, what is a decoder supposed to draw when it receives an intermediate (B/P) frame first? Green background with the changes on top? Looks shit. Most decoders will simply skip until the next keyframe.
Now, MPEG, among tons of other metadata, also stores timestamps for every s