I'm pretty sure the only real issue with the license is that the license is not clear about what the limits of "this software" are.

My understanding is that the following are your main concerns: 1. Content, including blog posts, talks, and images. You don't really want those reposted, especially if misattributed or altered. 2. I know you really don't want people to come to rely on the software have put out there on the net, especially in any way where you would feel obligated to provide support, notifications about vulnerabilities, etc.

For #1, clarifying that the contents of the `blog`, `gallery`, `talks` and `static` folders (and perhaps `template` too) are not part are not covered by the license, would effectively take care of this. (I also agree that it probably won't stop people from hosting such modified copies, especially if they are using scraping techniques, as opposed to running the code, but at least then it is completely unambiguous that they are violating the license.)

For #2 the existing nonstandard license, and warnings in the readme are probably mostly sufficient to make this clear. Plus honestly overall the code is pretty tailored to you. If I were to try to create a blog based on your code, I'd want to rip out the galley and talk sections, would need to redesign or remove the webmention support (or run a stripped version of the `mi` api), remove the patreon support, remove or modify xe-conv, change the cloud flare ping code, remove signalboost (I'd be too small to meaningfully boost anybody) etc. And all of that on top of creating the content, creating a stylesheet I like, creating new templates, etc.