simpleblog VS blog-programming

There's another dimension that nobody seems to talk about, and that's what happens with access to content is restricted. There is basically no censorship and no abuse from "those who can't get away with stuff on other networks" in the realm of SMS (or WhatsApp/WeChat/whatever your country uses). You can have a very healthy network if the authors are responsible for access control to their content. That's the idea behind my side-project of an easy-to-use, easy-to-selfhost private blog.[1]

When people want to use the platform to "become a thought leader" or "expand their network" then you're in the realm of public publishing which is where all the problems you cite become issues. The web makes privacy possible, and I don't understand why so few people are interested in that angle. For me I want to be able to share photos of my daughter with family and friends. I don't care if someone else wants to privately rant about the government to their friends--privacy enables both of these.

[1] https://github.com/mawise/simpleblog

Here is a failed deployment, with a single space character added since this successful deployment an hour before.

I have this scenario with my multiple blog sites, and I just use a different repo for each one's posts & images, with a shared "base" theme. For example this is the base theme, then each repo (e.g. programming blog) just has remote_theme: JakeSteam/[email protected] in the config. I looked into a few options along the way, and explained the approach in detail if you want more info.