Just no idea why and if it is timed based or they are detecting it somehow and slowly blacklisting ID's based on usage. I'm guessing that is also the reason for the other random cases too. My normal Twitch ID must be blacklisted from using that 'twitch-web-wall-mason' device ID. So it's somehow picking certain user ID's to fail on and can't be IP based. I then created a new test Twitch account on the private tab, logged into it and still no ads. Removed my IP and user ID, notice server_ads = true (SureStream). Here is the token response from the GQL request. Thought I would try this again, but I'm still getting ads (While logged in). uBlock Origin versionįirefox (Latest Stable) Operating System and version As the old whitelisted device ID is now no longer whitelisted, is should be removed. Actual behaviorĪd rate limit is not applied because of the set device ID being different to a normal user device ID. The Twitch ad rate-limit should be applied, however it seems Twitch has now blocked the whitelisted device ID that was being used. Disable UBlock and repeat the above steps and after a refresh of the page, an ad does not show because the rate limit is correctly applied.Refresh page and notice another ad shows.Go to a Twitch channel with a pre-roll ad.The device ID bypass should now be removed to prevent excess 0d3a193 A specific URL where the issue occurs Without UBlock enabled, once an ad is shown, a refresh of a page will not show an ad for a specified time limit. Each refresh of a page after an ad is now shown, will repeat an ad because it does not apply a rate limit on Twitch's side. The issue now is that because UBlock is using the same device ID when requesting the video access token, the Twitch ad rate limit is not being imposed on that whitelisted device ID. The scriptlet that blocked Twitch ads is now circumvented by Twitch. using a new, unmodified browser profile.I checked the documentation to understand that the issue I report is not a normal behavior.The issue is not present after wholly disabling uBlock Origin ("uBO") in the browser.I performed a cursory search of the issue tracker to avoid opening a duplicate issue.This is not a support issue or a question.I verified that this is not a filter issue (MUST be reported at filter issue tracker).
0 kommentar(er)
