Comment on Channel content acceptance
By “may post content to the channel”, do you mean that other channels can post to your channel? With the standard channel roles, this is only possible for connections. For the “Public” channel role, the default contact role is already configured to allow connections to post. For the “Personal” channel role, this is not the case with the default contact role.
In this case, you need to create your own contact role that allows wall posts and assign this to the desired connections.
If you also want to allow wall posts from ‘external’ channels (which are not connections), you must use the ‘Custom’ channel role and set the permission accordingly (this can go as far as ‘Anybody on the internet’). However, this is definitely not recommended, as it can turn your own channel into a “spam dump”. In principle, the only option that can be recommended is “Only those you explicitly allow” in combination with an appropriate contact role.
In this case, you need to create your own contact role that allows wall posts and assign this to the desired connections.
If you also want to allow wall posts from ‘external’ channels (which are not connections), you must use the ‘Custom’ channel role and set the permission accordingly (this can go as far as ‘Anybody on the internet’). However, this is definitely not recommended, as it can turn your own channel into a “spam dump”. In principle, the only option that can be recommended is “Only those you explicitly allow” in combination with an appropriate contact role.
>By “may post content to the channel”, do you mean that other channels can post to your channel?
This 'channel' term is a confusion. A 'channel' has been created with the option 'forum', intention that people could post content to the channel.
> With the standard channel roles, this is only possible for connections.
The channel forum created, with no connections.
> In this case, you need to create your own contact role that allows wall posts and assign this to the desired connections.
No idea what a 'wall post' is. There are no instructions to create a contact role when no connections exist.
This is precisely the feature that forum channels on Hubzilla make use of. Everything that is to be posted in the forum is posted as a wall-post to the forum channel. And anyone who follows the forum channel (i.e. is connected to it on Hubzilla) will now see everything posted there as a wall post in their stream (their timeline), even if they have no direct contact (a connection) with other forum users. Replies to such posts are consequently also distributed to all connections (followers). This makes it possible to run a forum.
A standard forum channel without connections is effectively dead. If you create such a channel using the default channel role ‘Community Forum’, only the channel owner can post there. However, nothing appears in anyone’s stream or timeline. It is an echo chamber. Nobody can post in the forum because the channel role does not allow it. However, if someone establishes a connection to the forum channel, it is brought back to life. The channel role defines the basic permissions for a channel… in other words, what others are allowed to see and do. Wall posting is not permitted. These permissions can now be extended using contact roles (though permissions granted by the channel role cannot be revoked). There is always a default contact role associated with every channel role. As the name suggests, these are permissions that only apply to connections… they have no effect on outsiders or visitors. And in a forum, the default contact role also includes the permission to post on the wall. So anyone who has a connection to a forum channel also has the permission to post on the wall there, i.e. to make posts in the forum. Anyone without a connection can only view the wall and its contents, but cannot post. A connection to the forum channel is therefore a prerequisite for participating in a forum.
And now back to the permissions (which are defined in roles… channel roles and contact roles):
The channel role determines which permissions the channel itself grants. The contact role makes it possible to grant connections (but only connections) further permissions. Every channel always has a default contact role, which varies depending on the channel role. For a channel without connections, this contact role has no effect, as it only applies to connections. You can also create your own contact roles to grant even more or different additional(!) permissions to specific connections.
Here is a table providing an overview of the standard channel and contact roles (CC0):
Image/photo
PDF-Version
Management of 'files' within a channel needs reduction in nerdy documentation, e.g. 'ocap' is meaningless.
Now, you may consider this a severe design flaw because it goes against your idea of how things must work. But this is the best way by far for forum admins to have control over who can do what in the forum.
I mean, how many classic Internet forums allow outsiders to post and comment? Does Reddit allow that? Does Hacker News allow that? Does Slashdot allow that?
No, they don't. None of them do. They all only allow members to post. Because allowing non-members to post would give them next to no control over how to keep certain people from posting.
And no, Superblock is not a solution either.
There no request for superblock functionality nor non-authentication access people, only advice/direction to instructions at recommended configuration.