I think they mean pull-through cache. https://shipyard.build/blog/how-to-docker-registry-pull-through-cache/

That person is missing the point that a randomized MAC will often get a different DHCP lease, and the MAC address is used in that, so the IP address will change.

On a trusted Wi-Fi network, disable MAC randomization on your clients, and if possible reserve an IP address for their non-random MAC address. Some devices have deterministic random per WiFi network, which could also work. In iOS this is WiFi network -> private WiFi address “fixed”. “Rotating” would cause your pihole problems.

This could be paraphrased as “GUI for the GUI settings, non-GUI for the non-GUI settings.” It’s not surprising to me that parts of Linux that run on systems that don’t have GUIs do not have GUI settings. I understand the frustration, but building those is more work, and more things that can break, go out of date, etc…

What if Linux presented its config files in an app like regedit? Would that be easier? I doubt it. But with complicated data structures, making a first-class app just to edit a specific text file or set of files on disk is a very low ROI for engineering hours.