While I've been quiet on Hubzilla for the last couple of weeks, I've been blogging as usual in my WordPress blog. I send post announcements to Twitter and Tumblr, provide a mail subscription link. I have been sending post announcements also to Mastodon and forgetting about Hubzilla. But now I see that's not exactly what I want.
When I send posts to Mastodon, they go automatically into the public stream of my chosen Mastodon instance (Fosstodon.org). I don't really want that to happen, according to my somewhat anti-social network or anti-Fediverse principle that posts should be openly available, but should not be placed automatically in front of anyone's eyeballs. If a post goes to a public stream, it means that persons who does not necessarily wish to see my posts will find them there. Here on Hubzilla, the reason I wasn't publishing full posts was that my personal instance has been cloned on Disroot, meaning, again, that posts would then enter Disroot's public stream.
The solution, I see, is to disconnect my Hubzilla channel from Disroot's hub, stop sending announcements to Mastodon, and simply send them to my Hubzilla channel instead, via WP's Hubzilla crosspost plugin. The public stream of my Hubzilla channel is seen only by me, since it's a personal instance that doesn't accept new users. In addition, I can just go ahead and include the whole blog post. Posts sent from WordPress's Hubzilla crosspost plugin aren't formatted very well (for example, there are no paragraph breaks), but anyone seriously interested can just follow the link back to WordPress.
The result is that I can maintain a presence on the Fediverse, without exposing posts to the public streams that exist on Fediverse public servers. Now, it's true that also Tumblr and Twitter sometimes highlight user posts, but that is unlikely to happen in my case, because what I'm sending there (brief blogpost announcements) are not sufficiently interesting.
