Reason is because the desktop version of YouTube is (still mostly? I think it’s depends on the content) using client side ad serving. On the iOS and Android app, you are getting server side ad serving, meaning the content and ads are coming from the same CDN address. So if you were to block the ad manifest address in Pi-Hole you’d also be blocking the content.
Pi-Hole only really works in a client side served world. Server side it’s harder if not impossible to get around. Server side implementations are more expensive to deploy, so that’s why it’s not as universal.
It’s not clear to me exactly how New pipe and Vanced get around it, but I’m assuming it’s just a browser wrapper?
Reason is because the desktop version of YouTube is (still mostly? I think it’s depends on the content) using client side ad serving. On the iOS and Android app, you are getting server side ad serving, meaning the content and ads are coming from the same CDN address. So if you were to block the ad manifest address in Pi-Hole you’d also be blocking the content.
Pi-Hole only really works in a client side served world. Server side it’s harder if not impossible to get around. Server side implementations are more expensive to deploy, so that’s why it’s not as universal.
It’s not clear to me exactly how New pipe and Vanced get around it, but I’m assuming it’s just a browser wrapper?