Documentation: Add note that single-instance blogs are private

[generic-pers0n]

Hello! I had recently setup my own WriteFreely instance over at https://gperson.h0stname.net. It is intended to be used as my own personal public blog, so I naturally thought that having a single-user instance would be the way to go. However, I just recently discovered that having a single-user instance only allows your blog to be unlisted, private, or password protected. It turns out that, at the current moment, you need to have a multi-instance blog.

I have a simple solution to this problem: simply update the documentation to mention that you must have a multi-user instance in order to have a public blog. I intend to submit a PR improving the documentation to mention this too.

Steps to reproduce (if necessary)

Steps to reproduce the behavior:

1. Setup a WriteFreely instance with single_user = true under [app] in your config.
2. Visit blog settings and go to the publicity section.

Expected behavior

Initially, I thought that having a single user blog would be allowed to be public.

Application configuration

I don't think it matters, but just in case it does, here's my config:

• Single mode or Multi-user mode? Multi-user mode
• Database? SQLite
• Open registration? No
• Federation enabled? Yes

Version or last commit: 0.15.1, installed from the Alpine Linux package repositories.

[thebaer]

Thanks for bringing this up! So first, I moved this to our documentation repository since it isn't specifically a bug -- but maybe this should just be a discussion?

In WriteFreely, "Public" specifically means Visible on the Reader page, and of course the Reader page is only available on multi-user instances. So that's why it behaves the way it does.

But maybe there's a simpler way to do this -- instead of showing "Unlisted" on single-user instances (which doesn't really make sense without the "Public" option), maybe we just call it "Public" or "Publicly Visible" if we want to differentiate it. What do you think?

[generic-pers0n]

Thanks for bringing this up! So first, I moved this to our documentation repository since it isn't specifically a bug -- but maybe this should just be a discussion?

Whooops! My apologies for making an issue in the wrong repo. I'm thankful it's been moved to the correct one now 😅

In WriteFreely, "Public" specifically means Visible on the Reader page, and of course the Reader page is only available on multi-user instances. So that's why it behaves the way it does.

But maybe there's a simpler way to do this -- instead of showing "Unlisted" on single-user instances (which doesn't really make sense without the "Public" option), maybe we just call it "Public" or "Publicly Visible" if we want to differentiate it. What do you think?

I honestly had not realized the settings were for the reader in the first place, so I would think if we clarify that those settings are for the reader. I think that would be a good start. Then, I think you could call the option "Publicly Visible", as it would still be publicly accessible but not easily discoverable.