I read in a different post that the code was misinterpreted to be a 5 second sleep before showing the video, but instead was waiting 5 seconds to execute some anti-ad-block script. Still pretty sleazy either way.

[–] A_Very_Big_Fan@lemmy.world 27 points 11 months ago* (last edited 11 months ago) (1 children)

There's a video going around of a guy using a useragent spoofer to prove that it only does this on non-Chromium browsers. So I don't think it's necessarily anti-adblock, but it could be interpreted that way when you consider Google's plans to implement DRM in Chromium.

[–] vpklotar@lemmy.world 7 points 11 months ago

Had a look at Louise Rossmans video yesterday about this and from what he showed he got it on all browsers.

Video: https://youtu.be/_x7NSw0Irc0?si=My5Nurw4XqdjDH8l

[–] Solemarc@lemmy.world 11 points 11 months ago

When I went rooting around to find it. I figured it was some QA process that starts 5 seconds after the video loads (the timer seems to be async and the code sends a promise off while it waits). Of course, it's all minified JS so it's a huge pain to read.