CosmicGiraffe

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

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.

And they're not going to pay millions to be the default for a browser that no one uses.

This assumes that the reviewer who gave the rating wasn't considering value as part of their scoring. I'd expect the reviewer to be scoring a TV based on his good it is compared to similarly priced competitors, not comparing to every other TV on the market

The upside of IANA doing it would be a standardised place for sites to move to. Without coordination, different sites would move to different TLDs, probably mostly based on what isn't already registered. IANA could create a new TLD for this and give existing whatever.io owners a chance to register whatever.iox before its generally available

It's marked solved, but since OP didn't post the solution:

-e uses basic regular expressions, where you need to escape the meta-characters ((|)) with a backslash. Alternatively, use extended regex with -E

$ echo a | grep -E "(a|b)"
a
$ echo a | grep -e "\(a\|b\)"
a
$ echo a | grep -e "(a|b)"
$ echo a | grep -E "\(a\|b\)"

The xz compromise having demonstrated that FOSS projects are totally immune to interference from state actors...

You're right, my bad. (Source: https://help.kagi.com/kagi/search-details/search-sources.html)