CosmicGiraffe

"Automatic winding", about 90% of the way through

What does the mealie integration enable? I assume it's providing foods that can be logged, but can you also pull stuff from mealies meal planning section & populate it into the diary?

Yes, exactly. The convention is to use the lowest address in the range (e.g. 192.168.1.0/24), since you're allowing a range of addresses rather than a single one.

The reason to do this is that many firewall rules will be based on sets of addresses - you might want to allow traffic from any device in your local network without having to add individual rules for each

You might want to use either a /24 address or a /32 address in a firewall rule, depending on what you're trying to do. The difference is that the /24 one refers to a set of IPs, while the /32 one applies to only one IP.

Say you're adding a firewall rule like iptables -A - s 192.168.1.123/32 - j ACCEPT. This will accept all traffic with the source IP 192.168.1.123. If instead you use iptables -A - s 192.168.1.123/24 - j ACCEPT, you'll accept all traffic with a source IP in the 192.168.1.123/24 subnet, which is all the IPs between 192.168.1.0 & 192.168.1.255.

In the case of your WiFi IP, the subnet does something different. It tells you which IP addresses you should expect to be able to contact directly, and which you need to contact via a router. 192.168.1.214/24 says that all the IPs between 192.168.1.0 & 192.168.1.255 can be reached directly, whereas IPs outside that range need to be sent to a router.

ip route will show you the routes a device knows about. It'll look something like this (simplifying a bit):

default via 192.168.1.1
192.168.1.0/24 dev wlan0 src 192.168.1.214

The first line is the default route, which is used when no more specific route exists. It says that you talk to these IPs by sending your traffic to 192.168.1.1 (your wifi router) and it'll send it on from there.

The second one says that for IPs in the 192.168.1.0/24, you directly talk to them using your wlan0 interface

Most UK house construction doesn't really allow for retrofitting cables in the way that seems to be common in the the US

They tested using a green light for the front brake light, not a red one

Sure, but that's not the setup you described in the original post. I think that's probably where your confusion is coming from - people are responding about a setup that's just a PiHole, not a PiHole plus router features to ensure that it's used.

Ultimately any setup that allows the device internet access is going to introduce some opportunities for tracking/telemetry/ads. If the vendor really wants to they could just channel all that data through a single HTTPS connection, along with the useful data you want to let the device access. You won't have any way to inspect that traffic and selectively block it, so you end up having to chose between blocking everything or blocking nothing.

Your setup sounds like it's reaching the privacy/functionality trade off that you want.

With a Pihole, you aren't preventing the device from reaching the internet, you're just refusing to provide it answers to its DNS requests. That means that it can't translate a domain name (example.com) to an IP address (1.2.3.4) using your DNS server. But there's nothing stopping it from using a different DNS server whose IP it has hardcoded, and nothing stopping it from then talking to anything on the internet once it has the correct IP to use.

In contrast, the other poster sounds to be using a firewall to apply ACLs. That means that the only way to reach the WAN is by passing over the firewall, and the firewall can apply rules about what traffic it allows. That prevents the device talking to a hardcoded DNS server, or talking to something on the internet if it alreadt knows its IP.

The other poster also talks about adding specific exemptions to these ACLs for specific services. So, e.g. letting the TV reach Jellyfin, but only Jellyfin & not all the other devices on the network. That reduces the risk of an attacker using the IoT device as a way to attack the rest of the network, since there's less stuff to attack. You're right that this is a fairly marginal gain for an IoT device which doesn't have WAN access anyway.

The downside of this approach is that the device enforcing the ACLs has to handle all the network traffic. That means it needs more processing power to take packets, apply the ACL rules and then decide whether or not to send it onward. The upside of a Pihole is that DNS is a relatively tiny amount of traffic, so it takes much less processing power to handle just DNS.

I don't think it's accurate to say that everyone can just decompile the code and reuse it. Decompiling and reverse engineering a binary is incredibly hard. Even if you do that there are some aspects of the original code which get optimised out in the compiler and can't be reproduced from just the binary.

The GPL uses copyright because it's the legal mechanism available to enforce the principles that the GPL wants to enforce. It's entirely consistent to believe that copyright shouldn't exist while also believing that a law should exist to allow/enforce the principles of the GPL.

I don't think anyone but you ever said he was irrelevant, or bragged about not knowing who he was. You're extracting a ton of meaning to a short comment which I just don't think is actually there

https://socialblade.com/youtube/handle/asmontv says there's over thousand youtube channels with more subscribers than him. He might well be large & influential in his niche, but it's unlikely that people outaide his niche will know who he is. Do you think you've heard of 1,000 biggest youtubers whose channels aren't about things you're interested in?

Pewdiepie, by comparison, is the 12th most subscribed channel on youtube. I think you're underestimating how much more famous that makes him with the general public.