In theory this is already the case; Self-hosting only really requires understanding DNS and the basics of running a Unix system if you just rent a VPS at say, H

In theory this is already the case; Self-hosting only really requires understanding DNS and the basics of running a Unix system if you just rent a VPS at say, Hetzner. Similarly, buying domain names is as easy as buying a phone number, probably even easier since ID legislation surrounding phone numbers is much stricter. NAT, TCP and UDP don't come into play unless you also plan on self-hosting your IP assignments or need to configure the firewall, which most people don't need to do (firewalls for webservers are usually already set up by the distro from my experience.) The problem is that the rest of the process is poorly documented (really... anything surrounding HTTPS; webservers require setting arcane config flags that all make sense once explained but why aren't distros just shipping sane SSL snippets that aim to get a good SSLLabs score/maintain older browser compat as needed, pretty much all these configs are shared across systems, certbot is cool but good luck parsing the documentation and woe be onto you if you do DNS-level verification with an unofficial plugin, the docs are all over the place) which creates this faux idea that you need to be a massive tech nerd to even begin self-hosting. The closest thing most people can follow is setting up shop at a shared hosting provider with a one-click WordPress installation (or other apps fitting in an AMP stack). That has been automated to the point where the enduser can reliably do it, but that pushes the limit of what you can really consider self-hosting.