51–60 of 75 posts
Imho the risk/consequences of a downtime don't justify having some hardware draining power. If all goes down ansible will have provisioned a new pi in no time.
Nevertheless i applaud the effort and am happy to have learned some things from the article
Earlier quoted context omitted.
Use YT on the web. If you have an iPhone, get Stop the Madness, which can make the ads very short and easily skippable. It also removes a lot of annoying web behaviors and is highly customizable.
Or, you know, pay for the content you consume.
A simpler solution: Deploy one Pi-Hole instance and then set clients to use Pi-Hole as the primary resolver and your ISP/router as the secondary. In the rare circumstance that the Pi-Hole device is down, you fallback and get the "normal" ISP DNS service.
Turns out the Pi-Hole Raspberry Pi had borked and wasn't answering at all, my computer was waiting for the primary DNS _every_time_ for multiple seconds before trying the secondary one.
What it should've done (IMO) is query both and pick the fastest.
Swapped to NextDNS and haven't looked back, I set it on my router and mobile devices once and that's it.
I am also running a Pi-Hole and have wondered about what happens when/if the Pi-Hole goes down. Is there a simple way to have a failover/fallback DNS configured rather than requiring two Pi's? On failure, I'd like my DNS to just fallback to my routers default DNS - yes I'd get ad's but I think that's acceptable.
It seems like concern over reliability of the PiHole is a common concern (between the original post and the comments). I guess I'm just not sure why. I just run one, and have for quite a while. I've never had any issues, which suggests to me that the probability of failure is pretty low. But more importantly, the impact of failure is (in my opinion) almost zero. It's a home network. If the PiHole has a problem, eithe…
A simpler solution: Deploy one Pi-Hole instance and then set clients to use Pi-Hole as the primary resolver and your ISP/router as the secondary. In the rare circumstance that the Pi-Hole device is down, you fallback and get the "normal" ISP DNS service.
If you can guarantee that the PiHole will always be fastest, it should be OK. But I'd be curious to see how you'd go about guaranteeing that.
I run a pihole but I've also got a OPNSense router. I was thinking of turning on the AdGuard Home thats fully supported in OPNSense as a secondary. in fact I think this is just prompted me to do that.
I settled on virtualising Opnsense and Adguard separately on a proxmox instance.
Earlier quoted context omitted.
> it's not like the Pi-Hole can block embedded ads in adware apps like YouTube on the iOS Thanks for the info. I thought this was possible and it was the sole reason why I considered setting one up. Now I procrastinated on that project long enough to learn I can cancel it.
Use YT on the web. If you have an iPhone, get Stop the Madness, which can make the ads very short and easily skippable. It also removes a lot of annoying web behaviors and is highly customizable.
Instead I sideloaded SmartTubeNext on my Fire TV and just live with the banner ads.
A simpler solution: Deploy one Pi-Hole instance and then set clients to use Pi-Hole as the primary resolver and your ISP/router as the secondary. In the rare circumstance that the Pi-Hole device is down, you fallback and get the "normal" ISP DNS service.
Earlier quoted context omitted.
Or, you know, pay for the content you consume.
Do ads on YouTube go away if you sponsor a channel? Patreon, etc? (Serious question)
YouTuber makes more money on average when a YouTube Premium user watches their video than what they would get from the ad-view if the person wasn't on Premium.
All in all it's reasonable IMHO. I might purchase it some time. The only issue is that this of course doesn't remove sponsorships baked into the videos, which annoy me just the same as the YT ads. So, I would still need Sponsorblock.