AmbiguousProps

The Midwest will have increasingly bad tornado outbreaks driven by climate change.

That's nuts.

I'd just use benchmarks from openbenchmarking.org and Passmark's cpubenchmark.net if you want to determine performance.

Lots of great suggestions. If you want one that will make you mad, Swindled is a great one about white collar crime. Podcaster is left leaning (outwardly so) and it's (sometimes) therapeutic to hear him talk about some of the topics.

Oh yeah, I totally forgot about that - mine does do this, and the LED is right in the bottom middle, and it's super bright.

It probably doesn't need to be - but it was required to set up. Before I had my shield, I allowed local connections for local streaming, but you are correct, it's probably no longer necessary.

Ah, yeah, OpenBSD would do it. You'd basically be limited to running it in a VM which would have severe overhead. For Linux based stuff, though, it has minimal overhead.

Perhaps, but greedy people who are willing to make weapons that kill children will definitely at least be annoyed that they're losing billions internationally. They're greedy corporations, after all.

Interesting, what OS are you running? I've never ran into one that it doesn't work on so that's surprising.

I would counter that disadvantage with this: due to testing constraints, docker containers are usually updated more quickly when there's a 0 day, and you don't have to patch your entire OS if one single container has one. It reduces operator overhead greatly, because that's what it's designed to do. Even if one of your containers has a vulnerability, because it's a container, it won't necessarily affect your entire system, depending on the vulnerability.

I suppose that it adds technical overhead (not sure I would call it severe though), but in my opinion the benefit of docker is how easy it is to spin up a new service, and how easy it is to update and maintain the containers.

So, I use regex to block all Roku domains on my network via pihole:

(ads|logs|cloudservices|image|images|web|prod.mobile|wwwimg|captive|customer-feedbacks|amoeba|amoeba2|sr|giga.sb|cs).roku(.admeasurement)*.com$

Then, possibly overkill due to the above, I used OpnSense firewall rules to block all traffic from my Roku tv. I think I just got fed up with seeing Roku spam in my pihole, as the above regex seems to completely "break" Roku.

After that, I set up FLauncher (following the method #2 instructions on the gitlab page) on my shield. This makes it so I only see the Roku launcher for a few seconds while the shield starts up, and then I'm dropped straight into flauncher. I chose flauncher because it's very simple and barebones, so you might want to explore other options if you want more advanced features. I don't really need those features since I'm usually using an app anyway.

Note that I did all of that after the tv was configured and set up, YMMV if it's a brand new tv as it may need to call home to do the initial set up.

I wonder how pissing off US defence contractors will go for Trump & co. I certainly wouldn't want to poke that bear.