I do agree that the phrasing may be poor, but I see where ingav is coming from, if you're using hosted Wordpress and only keep your data in the Wordpress CMS, if Wordpress disappears today, so does all of your content. Although, that may seem foolish to some of us, there are definitely people out there who do that.

Yup. I'm using Vim + Hugo + GitHub + Netlify in a similar fashion. Just edit my markdown post, git push and it shows up on my website. I used some other static hosting service previously, don't even remember which one, but switching was super easy as I just pointed the output to some other bucket. So the public web hosting provider is completely commoditized and easy to switch from.

Also, I like treating my blog as a version-controlled, declarative "codebase" that's just a bunch of plaintext files (no MySQL tables, XML or JSON to crawl through).

You don't own for example the comments in this platform or the post that you make on Facebook or writing platforms like substack, if you are using notion you don't your notes

The phrase to use would be something like data ownership. Something more specific.

I don't know, where do you draw the line? If I host it myself using nginx running on a VPS, does that count? Or still no, because I don't own the VPS?

What if it's a dedicated machine, colocated? What if it's at home, but I pay an ISP?

edit: Downvoted, care to explain why? I genuinely wrestle with this question. I self-host lots of services at home - and I also self-host services on a cloud VPS, which have better availability and security posture with regards to my home network for things I make public or semi-public. Some have told me this isn't "self-hosting" and I am not sure where the line is drawn.

The cloud VPS isn't self hosting if you don't own the server. It would be like saying that you self-host your email service because you opened a GMail account

So self-hosting refers to hosting the hardware, not the software? Does a colocated dedi count?