We’ll see.At the moment I see any ads, nor nags in YT, using userscripts instead of extensions, but anyway I’m going to keep an eye on what’s happening in Greasyfork and OpenuserJS regarding YT in the future, this in any case offers many more options than the castrated extensions that will be in the stores to be able to stay there.
Don’t be too optimistic, you probably haven’t seen it because it’s not being rolled out universally just yet; they like to A/B test their massive feature changes.
I am pessimistic about scripts being able to handle this, since it is a server side manipulation of streaming packets. It might be interesting if instead of seeing ads, a workaround is invented where the ad is not shown to user and video remains black and silent for that duration, and Google gets to hear such a thing has happened. If they get angry about it, it might reveal more about what they desire with forcing watching ads for people.
I’m not so pessimistic, as the proverb says, where there is a law, there is also a way around it.
There are many very capable devs who are screwed by YT and Google as well like us and in the script repositories they have a free hand, which as devs for extensions they do not have.
YT is the only problem for adblockers, even the inbuild blocker in Vivaldi works flawles, even cutting off cookie advices and some paywalls, only in YT it fails. But the userscript I use instead in YT work there even better than uBO, at least until now. Extensions are all limited by the imposed norms in the stores, more in the near future, it’s this because I trust more in scripts, at least for certain tasks… As said, we’ll see.
Inserting ad clips between DASH HLS packets seems to have done the trick for YouTube. RIP ad blocking on YouTube. Have fun I guess… :/
We’ll see.At the moment I see any ads, nor nags in YT, using userscripts instead of extensions, but anyway I’m going to keep an eye on what’s happening in Greasyfork and OpenuserJS regarding YT in the future, this in any case offers many more options than the castrated extensions that will be in the stores to be able to stay there.
Don’t be too optimistic, you probably haven’t seen it because it’s not being rolled out universally just yet; they like to A/B test their massive feature changes.
I am pessimistic about scripts being able to handle this, since it is a server side manipulation of streaming packets. It might be interesting if instead of seeing ads, a workaround is invented where the ad is not shown to user and video remains black and silent for that duration, and Google gets to hear such a thing has happened. If they get angry about it, it might reveal more about what they desire with forcing watching ads for people.
I’m not so pessimistic, as the proverb says, where there is a law, there is also a way around it. There are many very capable devs who are screwed by YT and Google as well like us and in the script repositories they have a free hand, which as devs for extensions they do not have. YT is the only problem for adblockers, even the inbuild blocker in Vivaldi works flawles, even cutting off cookie advices and some paywalls, only in YT it fails. But the userscript I use instead in YT work there even better than uBO, at least until now. Extensions are all limited by the imposed norms in the stores, more in the near future, it’s this because I trust more in scripts, at least for certain tasks… As said, we’ll see.