Support for post visibility in Madblog https://blog.fabiomanganiello.com/article/support-for-post-visibility-in-madblog

#madblog has now added support for custom visibility for your posts and articles.

You may not want everything you write to be published on your index or federated everywhere.

Madblog now allows you to easily tweak the audience of your posts.

Visibility levels

All the visibility levels (except for draft) map one-to-one with their corresponding meanings on the Fediverse.

• public: articles are rendered on the blog indexes and replies are rendered in the comments section.
• unlisted: articles are rendered under the /unlisted page, replies are rendered in the comments section.
• followers: articles are not rendered on the blog, replies are not rendered in the comments section (only visible to ActivityPub followers).
• direct: articles are not rendered on the blog, replies are not rendered in the comments section (only visible to tagged ActivityPub users).
• draft content is neither rendered on the blog nor federated.

Default visibility

You can configure the default visibility level for all of your posts on a global level via config.yaml:

default_visibility: public

Or MADBLOG_DEFAULT_VISIBILITY environment variable.

Per-post visibility

You can configure the visibility level of a post by using the visibility Markdown header:

# A private post

 [//]: # (visibility: direct)

@alice@example.com only you should be able to see this message

ActivityPub constraints

If a post is federated then YOU CANNOT change its visibility level. This is a constraint on ActivityPub itself. You should delete and re-created the post with a different audience instead.

If a post was already federated and you move it to Draft then the previously federated version will not be removed. No changes that you apply while it's a draft will be published until you change the visibility level back, but the latest federated version will still be available. If you want to delete it, then you should delete the associated file.

Security observations

Remember that Madblog, by design, has NO USERS, NO AUTHENTICATION and NO WRITE API.

Everything lives on the file system, and every Markdown file in the supported folders will have a public URL.

It means that everyone with the URL can access the content.

Be mindful about not sharing sensitive data, even in drafts or private messages. And, if you can, use non-easy-to-guess filenames for posts you want to keep private.