![\"PepeCyBs](\"https:\/\/klacker.org\/images\/default_profile_photos\/rainbow_man\/48.png\")
<\/a>PepeCyBs Welt<\/a> wrote the following post <\/a>Thu, 01 May 2025 19:58:29 +0200<\/span><\/span><\/div>My rules \u2013 my Hubzilla (en)<\/strong>
![\"Image\/photo\"](\"https:\/\/klacker.org\/photo\/ffd5fab0-985c-43f9-8397-eef1a177aeea-2.png\" "\\"\\"")
<\/a>
After recently writing a \u2018Hubzilla-H\u00e4ppchen<\/a>\u2019 on the topic of \u2018channel calming<\/a>,\u2019 I thought I would share my personal configuration here, along with some explanations... and perhaps show what a great tool Hubzilla is for participating in the Fediverse in a relaxed manner.
The channel roles<\/a> \u2018Public\u2019 and \u2018Personal\u2019 are a good choice for getting started and correspond to what you would expect from the Fediverse and social networks in general. However, these settings do not protect you from being annoyed by spam or receiving \u2018inappropriate\u2019 comments from strangers (i.e. participants without a connection).
To achieve this, you need to dip into Hubzilla's bag of tricks. With its sophisticated permission system, Hubzilla offers all the tools you need for an enjoyable Fediverse experience.
To do this, you need to select the \u2018Custom<\/em>\u2019 setting for the channel role.
This is done via Settings<\/strong> (in the main menu... the one with your profile picture... at the top of the navigation bar) \u2794 Channel Settings<\/strong>. There, select \u2018Custom<\/em>\u2019 from the \u2018Channel Role<\/em>\u2019 drop-down menu.
Then, set the permissions precisely under Settings<\/strong> \u2794 Privacy Settings<\/strong>. This is done by clicking on the \u2018Custom configuration of channel role<\/em>\u2019 button to switch to the role editor. You will first see a warning: \u2018Proceed with caution - Changing advanced configuration settings can impact your, and your contacts channels functionality and security.<\/em>\u2019 If you confirm that you want to take the \u2018risk\u2019, you will be taken to the configuration editor for the channel role.
First, you should think about what you want to allow whom on the Internet, in the Fediverse and in the Grid (the network of all Hubzilla hubs)... in other words, what rights you want to grant to others.
Below, I present my personal preferences. If you have other ideas, you must specify them for yourself and ultimately implement them in the channel role rules. This is therefore a highly individual decision... and everyone is entitled to their own opinion. There is no right or wrong here.
My idea for participating with my main channel is as follows: I want everyone on the internet \u2013 whether they have a Fediverse account or not \u2013 to be able to see my posts. This should be the case on other instances and also in my channel stream. In addition, everyone on the internet should be able to see my standard profile. However, my contacts (i.e. my connections) are nobody else's business. Only my connections should be able to see them. Everyone should also be able to see my media and images, as well as my websites and wikis.
However, I don't want to receive posts directly from strangers in my stream. And I don't want everyone to be able to edit my web and wiki pages or create new ones. I would much rather decide who is allowed to do that. I also only want to allow connections to post on my \u2018wall\u2019, i.e. directly in my channel stream. Strangers should not be able to like\/dislike or comment on my posts. This should also be reserved for my contacts. The same applies to chatting and repeating or sharing my posts. The administration of my channel is my business... and perhaps that of one or a few trusted individuals... in case I am unavailable for a longer period of time.
At this point, it is important to remember that Hubzilla's permissions are based on the whitelist principle<\/a>. The basis for this is the channel role. Everything that is permitted in this is generally permitted for the selected groups and cannot be removed elsewhere. With the contact roles, you can then grant further permissions (for all points for which you have set the permission \u2018Only those you explicitly allow<\/em>\u2019 in the channel role). However, you can create as many contact roles as you like with different additional permissions and assign them to different connections.
It is therefore advisable to be quite restrictive with the channel roles and to set most items to \u2018Only those you explicitly allow<\/em>\u2019.
Now I will go through the individual items in the channel role and show how I have set them...
1. Can view my channel stream and my posts -> Anybody on the Internet<\/em><\/strong>
This makes all my posts public so that everyone can see them.
2. Can send me their channel stream and posts -> Only those you explicitly allow<\/em><\/strong>
I will allow all my connections to do this for now via my own standard contact role, which I will create later.
3. Can view my default profile -> Anybody on the Internet<\/em><\/strong>
I also want everyone on the Internet to be able to see my default profile.
4. Can view my connections -> Only those you explicitly allow<\/em><\/strong>
I also grant this (my personal decision\/setting) to all my connections via my own standard contact role.
5. Can view my file storage and photos -> Anybody on the internet<\/em><\/strong>
Here, permission must be granted to everyone, because media and images are sometimes (mostly) shared in posts that everyone should be able to see.
6. Can upload\/modify my file storage and photos -> Only me<\/em><\/strong>
Only I am allowed to mess around with my files and folders. Period. End of story.
7. Can view my channel webpages -> Anybody on the Internet<\/em><\/strong>
8. Can view my wiki pages -> Anybody on the Internet<\/em><\/strong>
In both cases, this is public content... visible to everyone.
9. Can create\/edit my channel webpages -> Only me<\/em><\/strong>
My websites are my<\/strong> websites. Anyone who wants to create their own must register and create their own channel.
10. Can write to my wiki pages -> Only those you explicitly allow<\/em><\/strong>
I only allow certain connections to edit and create entries in my wikis. To do this, I have to create a separate contact role.
11. Can post on my channel (wall) page -> Only those you explicitly allow<\/em><\/strong>
I initially allow all my connections to do this via my own standard contact role.
12. Can comment on or like my posts -> Only those you explicitly allow<\/em><\/strong>
This is also only allowed for all my connections via my own standard contact role. This prevents comments from strangers.
13. Can send me direct messages -> Only those you explicitly allow<\/em><\/strong>
14. Can like\/dislike profiles and profile things -> Only those you explicitly allow<\/em><\/strong>
15. Can chat with me -> Only those you explicitly allow<\/em><\/strong>
These three permissions are also only for my contacts (my own default contact list).
16. Can source\/mirror my public posts in derived channels -> Only those you explicitly allow<\/em><\/strong>
I also only allow repeating and sharing (quote posting) via my own default contact role to all my connections.
17. Can administer my channel -> Only those you explicitly allow<\/em><\/strong>
If necessary, I will create an extra contact role for this purpose in order to grant certain, particularly trustworthy contacts this \u2018sacred task\u2019 if necessary.
Now a few words about the general privacy settings:
\u2018Automatically approve new contacts<\/em>\u2019 should remain disabled, because otherwise strangers could secure rights by \u201cfollowing\u201d your channel that I explicitly only grant to those with whom I establish a connection (i.e., mutual \u201cfollowing\u201d).
I also leave \u2018Accept all messages which mention you<\/em>\u2019 turned off because I don't want posts from strangers in my stream just because they mention my channel handle.
\u2018Enable OCAP access<\/em>\u2019, on the other hand, should be turned on. This allows you to see media in (Hubzilla) posts (especially in forum channels) even if the author\/owner has restricted their visibility.
You should think carefully about whether to enable \u2018Accept unsolicited comments for moderation<\/em>\u2019. If you do not enable this, strangers will not be able to comment on your posts. Comments will be discarded. If you enable it, accounts\/channels that you are not connected to can also comment on your posts. However, these will not be published immediately. You can decide (moderate) whether the comment should be accepted.
I have only very rarely received inappropriate comments or spam comments, so I have enabled this option. The reason? It is entirely possible (and has happened to me on several occasions) that a stranger has posted a \u2018successful\/appropriate\/special\u2019 comment on one of my posts... and I may have added them to my connections because of this. If I had left the option disabled, such \u2018encounters\u2019 would not have been possible.
If inappropriate comments start to take over at some point, I can always turn the option off again. That's my personal opinion... that's why I do it this way. Everyone has to decide for themselves.
Important... after you have made your custom settings and selected your options, be sure to click on the \u2018Submit<\/em>\u2019 button, otherwise all your work will be for nothing. \ud83d\ude09
I have now laid the foundation for my relaxed channel. All I have to do now is create a few contact roles to grant my connections the desired permissions. With this channel role, interaction with connections is initially as restricted as it is for strangers (\u2018Everyone on the Internet\u2019).
You can manage contact roles via the \u2018Contact Roles<\/em>\u2019 app.
The default contact role \u2018Standard<\/em>\u2019 is the system contact role and cannot be changed. I'll put that on hold for now by disabling the option \u2018Automatically assign this role to new contacts<\/em>\u2019.
I create my own default contact role. I have named it \u2018Default<\/em>\u2019. For this role, I now enable \u2018Automatically assign this role to new contacts<\/em>\u2019 so that all contacts I add from now on will be assigned this role.
To grant my connections the rights discussed above, I have configured the contact role as follows:
<\/a>After recently writing a \u2018Hubzilla-H\u00e4ppchen<\/a>\u2019 on the topic of \u2018channel calming<\/a>,\u2019 I thought I would share my personal configuration here, along with some explanations... and perhaps show what a great tool Hubzilla is for participating in the Fediverse in a relaxed manner.
The channel roles<\/a> \u2018Public\u2019 and \u2018Personal\u2019 are a good choice for getting started and correspond to what you would expect from the Fediverse and social networks in general. However, these settings do not protect you from being annoyed by spam or receiving \u2018inappropriate\u2019 comments from strangers (i.e. participants without a connection).
To achieve this, you need to dip into Hubzilla's bag of tricks. With its sophisticated permission system, Hubzilla offers all the tools you need for an enjoyable Fediverse experience.
To do this, you need to select the \u2018Custom<\/em>\u2019 setting for the channel role.
This is done via Settings<\/strong> (in the main menu... the one with your profile picture... at the top of the navigation bar) \u2794 Channel Settings<\/strong>. There, select \u2018Custom<\/em>\u2019 from the \u2018Channel Role<\/em>\u2019 drop-down menu.
Then, set the permissions precisely under Settings<\/strong> \u2794 Privacy Settings<\/strong>. This is done by clicking on the \u2018Custom configuration of channel role<\/em>\u2019 button to switch to the role editor. You will first see a warning: \u2018Proceed with caution - Changing advanced configuration settings can impact your, and your contacts channels functionality and security.<\/em>\u2019 If you confirm that you want to take the \u2018risk\u2019, you will be taken to the configuration editor for the channel role.
First, you should think about what you want to allow whom on the Internet, in the Fediverse and in the Grid (the network of all Hubzilla hubs)... in other words, what rights you want to grant to others.
Below, I present my personal preferences. If you have other ideas, you must specify them for yourself and ultimately implement them in the channel role rules. This is therefore a highly individual decision... and everyone is entitled to their own opinion. There is no right or wrong here.
My idea for participating with my main channel is as follows: I want everyone on the internet \u2013 whether they have a Fediverse account or not \u2013 to be able to see my posts. This should be the case on other instances and also in my channel stream. In addition, everyone on the internet should be able to see my standard profile. However, my contacts (i.e. my connections) are nobody else's business. Only my connections should be able to see them. Everyone should also be able to see my media and images, as well as my websites and wikis.
However, I don't want to receive posts directly from strangers in my stream. And I don't want everyone to be able to edit my web and wiki pages or create new ones. I would much rather decide who is allowed to do that. I also only want to allow connections to post on my \u2018wall\u2019, i.e. directly in my channel stream. Strangers should not be able to like\/dislike or comment on my posts. This should also be reserved for my contacts. The same applies to chatting and repeating or sharing my posts. The administration of my channel is my business... and perhaps that of one or a few trusted individuals... in case I am unavailable for a longer period of time.
At this point, it is important to remember that Hubzilla's permissions are based on the whitelist principle<\/a>. The basis for this is the channel role. Everything that is permitted in this is generally permitted for the selected groups and cannot be removed elsewhere. With the contact roles, you can then grant further permissions (for all points for which you have set the permission \u2018Only those you explicitly allow<\/em>\u2019 in the channel role). However, you can create as many contact roles as you like with different additional permissions and assign them to different connections.
It is therefore advisable to be quite restrictive with the channel roles and to set most items to \u2018Only those you explicitly allow<\/em>\u2019.
Now I will go through the individual items in the channel role and show how I have set them...
1. Can view my channel stream and my posts -> Anybody on the Internet<\/em><\/strong>
This makes all my posts public so that everyone can see them.
2. Can send me their channel stream and posts -> Only those you explicitly allow<\/em><\/strong>
I will allow all my connections to do this for now via my own standard contact role, which I will create later.
3. Can view my default profile -> Anybody on the Internet<\/em><\/strong>
I also want everyone on the Internet to be able to see my default profile.
4. Can view my connections -> Only those you explicitly allow<\/em><\/strong>
I also grant this (my personal decision\/setting) to all my connections via my own standard contact role.
5. Can view my file storage and photos -> Anybody on the internet<\/em><\/strong>
Here, permission must be granted to everyone, because media and images are sometimes (mostly) shared in posts that everyone should be able to see.
6. Can upload\/modify my file storage and photos -> Only me<\/em><\/strong>
Only I am allowed to mess around with my files and folders. Period. End of story.
7. Can view my channel webpages -> Anybody on the Internet<\/em><\/strong>
8. Can view my wiki pages -> Anybody on the Internet<\/em><\/strong>
In both cases, this is public content... visible to everyone.
9. Can create\/edit my channel webpages -> Only me<\/em><\/strong>
My websites are my<\/strong> websites. Anyone who wants to create their own must register and create their own channel.
10. Can write to my wiki pages -> Only those you explicitly allow<\/em><\/strong>
I only allow certain connections to edit and create entries in my wikis. To do this, I have to create a separate contact role.
11. Can post on my channel (wall) page -> Only those you explicitly allow<\/em><\/strong>
I initially allow all my connections to do this via my own standard contact role.
12. Can comment on or like my posts -> Only those you explicitly allow<\/em><\/strong>
This is also only allowed for all my connections via my own standard contact role. This prevents comments from strangers.
13. Can send me direct messages -> Only those you explicitly allow<\/em><\/strong>
14. Can like\/dislike profiles and profile things -> Only those you explicitly allow<\/em><\/strong>
15. Can chat with me -> Only those you explicitly allow<\/em><\/strong>
These three permissions are also only for my contacts (my own default contact list).
16. Can source\/mirror my public posts in derived channels -> Only those you explicitly allow<\/em><\/strong>
I also only allow repeating and sharing (quote posting) via my own default contact role to all my connections.
17. Can administer my channel -> Only those you explicitly allow<\/em><\/strong>
If necessary, I will create an extra contact role for this purpose in order to grant certain, particularly trustworthy contacts this \u2018sacred task\u2019 if necessary.
Now a few words about the general privacy settings:
\u2018Automatically approve new contacts<\/em>\u2019 should remain disabled, because otherwise strangers could secure rights by \u201cfollowing\u201d your channel that I explicitly only grant to those with whom I establish a connection (i.e., mutual \u201cfollowing\u201d).
I also leave \u2018Accept all messages which mention you<\/em>\u2019 turned off because I don't want posts from strangers in my stream just because they mention my channel handle.
\u2018Enable OCAP access<\/em>\u2019, on the other hand, should be turned on. This allows you to see media in (Hubzilla) posts (especially in forum channels) even if the author\/owner has restricted their visibility.
You should think carefully about whether to enable \u2018Accept unsolicited comments for moderation<\/em>\u2019. If you do not enable this, strangers will not be able to comment on your posts. Comments will be discarded. If you enable it, accounts\/channels that you are not connected to can also comment on your posts. However, these will not be published immediately. You can decide (moderate) whether the comment should be accepted.
I have only very rarely received inappropriate comments or spam comments, so I have enabled this option. The reason? It is entirely possible (and has happened to me on several occasions) that a stranger has posted a \u2018successful\/appropriate\/special\u2019 comment on one of my posts... and I may have added them to my connections because of this. If I had left the option disabled, such \u2018encounters\u2019 would not have been possible.
If inappropriate comments start to take over at some point, I can always turn the option off again. That's my personal opinion... that's why I do it this way. Everyone has to decide for themselves.
Important... after you have made your custom settings and selected your options, be sure to click on the \u2018Submit<\/em>\u2019 button, otherwise all your work will be for nothing. \ud83d\ude09
I have now laid the foundation for my relaxed channel. All I have to do now is create a few contact roles to grant my connections the desired permissions. With this channel role, interaction with connections is initially as restricted as it is for strangers (\u2018Everyone on the Internet\u2019).
You can manage contact roles via the \u2018Contact Roles<\/em>\u2019 app.
The default contact role \u2018Standard<\/em>\u2019 is the system contact role and cannot be changed. I'll put that on hold for now by disabling the option \u2018Automatically assign this role to new contacts<\/em>\u2019.
I create my own default contact role. I have named it \u2018Default<\/em>\u2019. For this role, I now enable \u2018Automatically assign this role to new contacts<\/em>\u2019 so that all contacts I add from now on will be assigned this role.
To grant my connections the rights discussed above, I have configured the contact role as follows: