-
Notifications
You must be signed in to change notification settings - Fork 61
Not currently blocking ads anymore #3
Comments
Yes the script currently doesn't work as stated in the Reddit post. Also I have never recommended Alternate Player? Nov 8th edit: #3 (comment) |
I never said you recommended it, a lot of people have been, I felt like saying that it wasn't worth the trade off for me beforehand in case you do, I think it just came off wrong |
what if we override the access_token response and set the 3 variables (or more) regarding ads to disable them. It would look something like this:
doubt the ads could be controlled client side, but maybe it would work? I can override it in console, but not with ublock (probably missing something stupid). |
You can try using UserScript managers like ViolentMonkey |
I haven't thoroughly tested but setting the query params "player_type" to "mobile" and "platform" to "android" seems to fix, ie:
and
|
still got an ad but seems less frequent than without that patch. They probably serve less ads to mobile users? |
After making the changes I mentioned, if I refresh the page after an ad shows up it goes away. I think that's why people are using userscripts to automate this. |
Hey folks. Just released a Chrome/Firefox-extension version that should block ads. Give it a try: https://github.com/odensc/ttv-ublock/tree/extension (instructions in readme) Remove any previous uBlock script you may have installed. |
This seems to be working on initial tests. |
do we have to re-download it every time twitch patch fix? |
It doesn't work. |
The new chrome extension is working great! Thanks for your hard work @odensc |
I know that Twitch has been restricting the player to 360/480p and you edited the script recently in an attempt to mitigate those changes, however, the script now no longer actually blocks the ads. Also, don't recommend Twitch alternate player, that thing has like 30s of delay.
Edit from maintainer:
Please try the latest standalone extension version, which should block ads as of Nov 8th: #3 (comment)
The text was updated successfully, but these errors were encountered: