It works by subvolume, which are not equivalent to partitions.

Some devices will use a hard coded DNS instead of respecting the one on the network

Right, and I am pointing out that non-cooperative devices still won’t be blocked by pihole if they so desire.

Right, so flowing that link there are three ways for DNS:

Classic on port 53,

Dns over TLS on port 853

Dns over https.

The first two can be blocked, because they have specific ports exclusively assigned to them. DoH can’t be blocked reliably, because it is encrypted and on a common port. Though blocking 443 on common DNS resolvers can force some clients to fall back to one of the variants that can be blocked/redirected

Dns over https is immune to that firewall method, right?

It’s a fundamental property of the federated system. The devs need to acknowledge it the same way you need to acknowledge that people can lie. It’s a fact, there is no easy way around it and everyone knows it.

So true! Ew FDP!

True, don’t know how I missed that.

Or just a hardcoded IP, lol

Yes. Wifi is 2.4 GHz, speed of light is 0.3 Gm/s. Therefore one wavelength is 0.3/2.4 m/s/Hz = 12.5 cm

So

• 22% more screen
• twice the pixels
• the same number of cores, though undoubtedly faster
• four times the ram
• 2 to 32 times the storage

Not that impressive for ten years of development to be honest. In addition to that there are limits to what is required for everyday usage. Not to make a “640k should be enough for everybody”, but browser and messaging only requires a few GB of RAM and will do so for the foreseeable future. 8GB is future proof enough for the vast majority of use cases.

I have 2TB of storage in my PC. The actually important part (documents and programs) take up minuscule amounts of space. The remainder is for AI models, movies and games, all of which I could delete and download again.