Looking inside those m3u8 responses, the hostnames of those transport stream (ts) urls contain "video-weaver", and inside the m3u8 there are some infos about "stitched" ads, triggers and whatnot. Obfuscation is the keyword here, and it makes understanding whats going on there very hard to nearly impossible. Unfortunately those are minified and assembled versions, so just pretty printing them wouldnt yield useful variable names and stuff like that. You can see some banner / log message in the console denoting it as "Amazon IVS version 1.15" or something along the lines. I think this wasm binary is the actual video player. Just by looking into chromes developer tools, it seems that there is a js service worker and a wasm worker doing a sequence of requests to cryptically-long named m3u8 urls. You have to keep in mind that those changes not roll out at the same time everywhere in the world and that just like last time when a Twitch team was actively battling ad blocking they very frequently do releases and just within few hours the behavior of ad blocking might change. This is probably because to do with the playertype currently being used by vaft and changes to that type by the Twitch team as mentioned above.Įdit: Mid-rolls can currently not be blocked via TTV LOL as I just saw in an ad heavy real stream. This test stream always gives you pre-roll ads and I could verify the behavior mentioned above with it: If you only use vaft you will currently get the "commercial break in progress" sign as OP provided. It doesn't matter that you have both vaft and TTV LOL installed as the latter one just has priority over the script apparently. It's very easy to verify that pre-roll ads are actually still successfully blocked (at least in my country) via TTV LOL. After having issues with vaft as described in this post I added TTV LOL with vaft and the issue went away, at least for me anyway.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |