Last time I had a Roku you could block the static home screen ads with PiHole. So as long as they don’t start serving these from the same domain as something you need for the box to work right or start hard coding a different DNS server into the OS that won’t respect your local network settings it will probably keep working.
But if they are not doing one of the above to get around DNS adblockers yet, they will eventually in the name of those sweet sweet ad dollars. Best to just start planning an exit from Roku products if you care about such things.
If shit like this keeps going, soon my car is going to be homemade out of 2x4s and a backyard-forged 2 stroke engine, while I try to turn sand into chips so I can stay connected to the Internet…
Yes, in that pihole can filter ad servers, but no because backup DNS servers are hard coded in the software; you have to block those too from your router.
I’m wondering if they managed to break that, too. I tried forcing my Roku to use my pi-hole by blocking Google DNS (what it seems to be hardcoded with) at my router and the Roku just stops recognizing that it even has an Internet connection.
At first, Pi-hole was enough, but some devices had a software update a year or two ago that used Google (if memory serves) DNS as a backup. It was sneaky, but adding a block rule closed that loophole.
Not all devices had that change though. I’m hoping mine is old enough to be ignored for the new video ads.
Can you block these by adding Pi-Hole? I’m so tired of enshittification.
Better alternative, stop buying Roku products…
And do what instead? Serious question as I’m about to buy my 2nd roku product
I like Android TV but there are a lot of better other solutions like using a SBC or a Chromecast.
Last time I had a Roku you could block the static home screen ads with PiHole. So as long as they don’t start serving these from the same domain as something you need for the box to work right or start hard coding a different DNS server into the OS that won’t respect your local network settings it will probably keep working.
But if they are not doing one of the above to get around DNS adblockers yet, they will eventually in the name of those sweet sweet ad dollars. Best to just start planning an exit from Roku products if you care about such things.
If shit like this keeps going, soon my car is going to be homemade out of 2x4s and a backyard-forged 2 stroke engine, while I try to turn sand into chips so I can stay connected to the Internet…
https://www.openmotors.co/product/tabbyevo/
Bit out of date, but it’s a framework to start with.
I’ve already resolved to not buy cars newer than the ones I already have (from the '90s and 2000s).
(It sucks 'cause it means I can’t have an EV unless I find one of those super-low-volume '90s fleet compliance cars or build my own.)
You can always install an EV conversion kit to old cars.
Consider an ebike to supplement your car for shorter trips. I’ve just opted to ride my bikes more.
My ebike odometer ticked over 1000 miles a couple weeks ago.
Currently, yes and no.
Yes, in that pihole can filter ad servers, but no because backup DNS servers are hard coded in the software; you have to block those too from your router.
Not sure about the new changes planned.
I’m wondering if they managed to break that, too. I tried forcing my Roku to use my pi-hole by blocking Google DNS (what it seems to be hardcoded with) at my router and the Roku just stops recognizing that it even has an Internet connection.
I haven’t seen a seen a single home screen Roku ad since I installed Pi-Hole.
This will be my last Roku, it has become such a horrible ad-ridden experience since I first got it years ago.
At first, Pi-hole was enough, but some devices had a software update a year or two ago that used Google (if memory serves) DNS as a backup. It was sneaky, but adding a block rule closed that loophole.
Not all devices had that change though. I’m hoping mine is old enough to be ignored for the new video ads.
I imagine they’ll eventually work around block rules with DNS over https.
Then you block that too at the router level (port 853 if my memory is correct)
DNS over TLS (aka DoT) uses port 853. DNS over HTTPS (aka DoH) uses port 443 so that it looks the same as any other web traffic for privacy reasons.