In that sense, everything is "fully owned" and the phrase is meaningless. But in the context of the summary where you're using it, it certainly sounds like you are claiming ownership on the infrastructure

You're getting a lot of pushback but I agree with the sentiment of fully owned. Sure, the git repo and static files are hosted elsewhere for now. But you can easily switch that place any time. Meanwhile all the important stuff: the post data, the code to format them, the domain name, the process itself. That's all in your complete ownership and control. It's a very different bargain than, say, hosting things at wordpress dot com.

I'd go for fully static, which can be served everywhere.

I think blogs should be built like this to make preservation easier. I'd love to have something that make content domain agnostic, more like git that allows cloning and distributing content without forcing people to guess when to pull and archive if they want to keep track of things.

I see, I do agree it is nice to have your data fully owned (like really) and safe on device (or devices), though, sometimes it doesnt feel like enough in the ever changing landscape of the internet.

But if they kill your access to those accounts do you have a method to force them to let you back in to get “your” content? Serious question as I self-publish and use a distribution service for my music but I stop short of your claim. I’m an independent rights holder. I don’t own the platforms upon which I choose to distribute my work - terminology does matter and, well, you’re claiming something basically untrue because it sounds cool…that’s my impression.