It blocked YouTube ads when ads where served from other domains or subdomains. Now that they’re served from the same subdomains as videos, it’s not blocking anymore.
all these people missing the part where I said “holding a shotgun” – I guarantee you’ll never see a YouTube ad on your network again if no data from their servers ever gets past your router. It’s not a subtle or precise option, but it is highly effective. Much like a shotgun.
Then you can just use peertube, piped, or invidious when that gets fixed
never underestimate the tenacity and ingenuity of spiteful pirates. It’s been a while since I last used invidious, but I can’t imagine it being permanently broken. in the meantime – Piped, then?
There has been some back and forth between Goolag’s countermeasures and Invidious’ countermeasures before arriving at the current situation, Invidious seemingly having lost the battle.
From their git issue tracker:
Hello,
Sad news for everyone. YouTube/Google has patched the latest workaround that we had in order to restore the video playback functionality.
Right now we have no other solutions/fixes. You may be able to get Invidious working on residential IP addresses (like at home) but on datacenter IP addresses Invidious won’t work anymore. (Some datacenter IPs may still work, but that’s a matter of time until they don’t anymore.)
…
This is not the death of this project. We will still try to find new solutions, but this might take time, months probably.
You can still self-host Invidious. I’m doing this for 1-2 weeks without any problems. What does not work: Public instances hosted in data centers, because YouTube blocked lots of cloud IPs.
Because I frequently use mpv, yt-dlp or a combination of both, the value I find in Invidious is in being able to conduct video searches against Youtube. And luckily that still works on public instances.
not pictured: the pihole just out of frame, holding a shotgun
??? Pihole never blocked YouTube ads.
It blocked YouTube ads when ads where served from other domains or subdomains. Now that they’re served from the same subdomains as videos, it’s not blocking anymore.
Google bought YouTube before there were ads. The ads were always Google’s own ads from their own domains so Pihole could never block them.
How do you use Pihole to block YouTube ads?
Block youtube.com. Quite effective, if you ask me.
all these people missing the part where I said “holding a shotgun” – I guarantee you’ll never see a YouTube ad on your network again if no data from their servers ever gets past your router. It’s not a subtle or precise option, but it is highly effective. Much like a shotgun.
Then you can just use peertube, piped, or invidious when that gets fixed
Invidious is currently out of order. Not sure if they would be able to cut out the ads.
never underestimate the tenacity and ingenuity of spiteful pirates. It’s been a while since I last used invidious, but I can’t imagine it being permanently broken. in the meantime – Piped, then?
If things get real stupid, we might have to employ AI to identify and strip ads from videos before mirroring. edit: Someone has, in fact, already trained an AI to identify ads in a video, with apparently 97.4% accuracy. So, the hard part’s already been done.
There has been some back and forth between Goolag’s countermeasures and Invidious’ countermeasures before arriving at the current situation, Invidious seemingly having lost the battle.
From their git issue tracker:
You can still self-host Invidious. I’m doing this for 1-2 weeks without any problems. What does not work: Public instances hosted in data centers, because YouTube blocked lots of cloud IPs.
Because I frequently use mpv, yt-dlp or a combination of both, the value I find in Invidious is in being able to conduct video searches against Youtube. And luckily that still works on public instances.
Piped wasn’t working earlier.
Newpipe works on Android and Freetube works on Linux. I guess a local invidious instance works, too. But then, you’d lose pooling.