I'm one of the creators of Leaflet - https://leaflet.pub - also mentioned in another comment. We're making a publishing app kind of like Substack or Ghost, but connected to the open social ecosystem building on AT Protocol. There a lot of potential here, and a lot of tools that already exist.
We collaborated with other publishing apps (pckt & Offprint) to make Standard.site - https://standard.site - a simple set of standards for publishing interop that enables something like RSS but on top of a whole social network. More context: https://lab.leaflet.pub/3moomxyjssk2p
Others can leverage this to make e.g. a whole reader app where you can find everything people in your network are publishing: https://standard-reader.app
A key thing is it's very flexible, you can publish on Leaflet, or on a self-hosted blog, and make your content discoverable and subscribeable in the same way. And in either case, you own your content — even if you use Leaflet as your hosted CMS, published data lives in your PDS where you control it, and all the social graph stuff persists even if you stop using Leaflet or we ever shut down.
Self-hosting a website is great but also considerable overhead for many folks, and we want to make it easy to publish and still have control and avoid lock-in. We even see folks doing hybrid approaches, e.g. using Leaflet to publish (for easy to use CMS + nice social features) but also pulling published data to render directly on their own website.
It's very different from what you get with a concentrated single platform like Substack (or Instagram, YouTube, etc) as far as audience reach, and early days with the ecosystem, but I think it's valuable in a different way. It's more aligned with the open web, and importantly, it's more antifragile — there are many ways to reach people and interact with your readers, from Bluesky to Leaflet to other reader apps, search tools, etc. Network effects aren't there yet to the degree of Substack, but a lot of cool things are emerging and it feels like an exciting time to build here together.
I get a cloudflare 502 error for standard.site