

IMHO the key aspect isn’t where you host things but rather understanding how hosting itself works.
To me the most challenging aspects are how to :
- route traffic
- start a service
- backup your data
and also ideally
- have more than 1 service on a single machine
- restore your data
- restore your entire setup
For that very first step I would say having a machine directly exposed to the Internet makes it easier. I don’t know what ISP you use but at least in Belgium where I’m currently located all ports are closed and IP are dynamic. That means if you want to show your freshly started Apache Web server to your mother in law it will challenging.
Meanwhile if you do manage to get to the last step, namely restore your entire setup, then restoring to a cloud service or a RPi is the same, you transfer your data, start your services and voila, you are back either LAN only or on the entire Internet via a cloud provider.
So autonomy isn’t as much as to where things are physically hosted and by whom as in the actual capacity to able to host there or elsewhere.
Finally if you are using a commercial ISP, as opposed to having your own AS, are you really self-hosting?



Come on people, think of the shareholders! /$
Slop, MicroSlope, MacroSlop, it’s BS all the same.