#Help -

#Help

2025-01-08 08:43:29

adminsforum@hubzilla.org

David Palk wrote the following post Wed, 08 Jan 2025 08:43:29 +0100

#Help

I'm still struggling to get any traction here.
My interests are firly eclectic but it doesn't sem to mater under what heeading I post/share I get null response.
I ca't be the only 'over educated' English speaking politicos using this platform.
What do I need to do?
A dummies guide would b helpful.

show all 32 comments

2025-01-08 10:04:20

Der Pepe (Hubzilla) ⁂ ⚝

pepecyb@hub.hubzilla.hu

@David Palk

Are you fundamentally new to Fediverse?

Then a few basics are worth knowing. There is no algorithm in the Fediverse that flushes posts (including your posts) into the stream (timeline) of other users. The Fediverse lives from contacts. You only get interaction via contacts (and then possibly also via the contacts' contacts).

Since you have chosen Hubzilla, have a look at the directory (all three ‘Directory Options’ set to ‘switched off’):

/directory

There you can search for interests and find possible contacts.

I'll be happy to put together a few more links to information for you later today.

2025-01-08 14:23:15

David Palk

palky@hub.netzgemeinde.eu

Thank you. That would be so useful and much appreciated.

2025-01-09 13:26:35

dynamic_hubzilla

dynamic@hub.netzgemeinde.eu

@David Palk

I feel mixed about Mastodon/Hubzilla federation because the two platforms are only sort-of compatible, but the reality is that most of my contacts are actually on Mastodon. When I first joined the Fediverse (as a Mastodon user), one of the things that helped me get started with finding people was the curated lists service Trunk: https://communitywiki.org/trunk/

This was years ago, and I'm not sure whether it's been kept current, but it might still be a useful resource?

The below guide is also Mastodon-specific and is based on experiences pre-Twitter-Muskopocalypse, but might also give you some ideas:
https://alexandra-thorn.dreamwidth.org/56151.html

Aside from differences in interfaces, a big difference between Mastodon and Hubzilla is that Mastodon is designed for social "reach", Twitter-style, while Hubzilla is engineered to give users control over who we connect with (more like Livejournal). That means that unless your Hubzilla settings are just right, you might have a harder time getting search tools to work than you might hope. The searching directory that Pepe mentioned should work, though! It also means that (again, depending on the settings you are using) it might be hard or impossible for other users to find *you*.

I also have the impression that Hubzilla is just smaller, especially if you're constrained to English-language.

Let me know if you have more questions!

2025-01-09 14:34:50

Scott M. Stolz

scott@loves.tech

If you have your channel set to "personal" then only your connections can see your posts. Your posts are not public. This limits who can see and interact with your channel.

If you want new people to see your posts, you have to make them public.

That might be why you have little interaction. Only your friends can see your posts.

2025-01-09 14:47:36

Frank Casa

frank@frank.casa

@David Palk When I visit your profile, I don't see any posts.

2025-01-09 14:49:07

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@Scott M. Stolz I think that's actually a big issue with Hubzilla: There are two channel roles for personal channels, but both were created over a dozen years ago for a vision of the Hubzilla grid of the mid-2010s. Neither of the two are really appropriate for today's Fediverse.

"Public" is too lax and will get your stream flooded, once you have a few hundred Mastodon contacts. "Personal" is too restrictive in a way that can impossibly be patched up with contact roles. It'd be secure enough if the Hubzilla grid was an enclosed thing, but it's too limited for a Fediverse where Hubzilla is tiny.

@David Palk I'm currently working on a getting started guide for fresh Hubzilla users, and I've got the channel role covered already. Here's an excerpt that might help you:

Channel role

Let's start with the channel role. For a personal channel, there are two preset channel roles: Public and Personal.

The Public channel role permits almost everything. This sounds convenient.

But trust me: The longer you'll use Hubzilla, and the more contacts you'll have who have connected to you first, the more control you'll want over who is allowed to send you their posts. Sure, you can ignore (mute) contacts, but that'd affect their comments and their direct messages all the same, and you may not want that. All you may want is to rid your stream and your list of unread activities of uninteresting cruft. You can only achieve that with permissions. This alone is a reason not to use the Public channel role.

The Personal channel role is more restrictive and relies on contact roles for permissions.

The catch: The Personal channel role doesn't give permission to like, dislike and comment on your posts. This made the most sense from the point of view of 2012 when Hubzilla was still Red or the Red Matrix, and there was still the idea of a "grid" of Red Matrix instances as a safety-centred decentralised network where it'd be totally normal to not be able to comment on anything and everything.

Today's Fediverse, however, doesn't know permissions. You'll soon have more Mastodon contacts than Hubzilla contacts. And on Mastodon, pretty much everything is permitted, and the idea that this could not be the case is entirely non-existent. Thus, the Personal channel role is too restrictive for today's Fediverse. Choosing it doesn't even make sense if you really don't want anyone and everyone to comment on your posts. That's because it can't keep Mastodon users from replying to you. Everyone will still be able to reply to you, but you won't see these replies, and they won't know that you don't see their replies.

So, in order to prepare your channel for today's Mastodon-normative Fediverse, only the Custom channel role is appropriate.

Choose the Custom channel role

The channel role can be selected in the channel settings which can be found in the channel menu on the left of the navbar or here: /settings, right at the top.

First set your channel to Personal. Submit the change. The set it to Custom so that Custom will take over the settings from Personal. Submit the change again.

While we're here, let's take care of some more business.
Select the correct timezone if you haven't already.
The default post location can be ignored. That is, if you wish so, you can add your real-life location, and be it ZZ9 Plural Z Alpha (which, technically speaking, is accurate), or whatever else you think of. It's a bit like the location field in bulletin-board forums.
Use browser location: Unless you're on mobile all the time, and your mobile browser knows where you are with your phone, and unless you really need everyone to know where you are, leave this off.
Adult content: This switch flags your entire channel NSFW. You can most likely leave this off unless you're going to post porn all the time.
Default photo upload folder, default file upload folder: You're good with the defaults.
Expire other channel content after this many days: This is for wiping posts from your contacts from your stream when they've reached a certain age. I guess you'll need a very good reason to have that done earlier than pre-defined on your home hub.
Do not import posts with this text and Only import posts with this text: These are Hubzilla's channel-wide filter lists. You probably won't need them yet.

Adjust the Custom channel role

Now, curiously, you can't customise the Custom channel role in the same place where you choose it. One aspect of Hubzilla's confusing and chaotic UI.

The settings for the Custom channel role can be accessed from the privacy settings page: /settings/privacy. It's in the bottom right corner: Advanced configuration. Click it, and you'll be presented a warning. If you mindlessly tinker around with your channel role settings, your channel may malfunction. But seriously, if you stick with Hubzilla's presets, your channel may malfunction in today's Fediverse as well. So: Accept the risk and continue.

Don't worry, though: I'll guide you through this.

The configuration dialogue which opens afterwards shows you how channel roles work, and what permissions and permission levels they include, namely seven or eight levels, depending on the permission.

There are up to eight permission levels for each permission:
Anybody on the internet: Exactly this. This level is only available where it makes sense.
Anybody authenticated: When it comes to sending you stuff or reacting upon your stuff, any Fediverse user. When it comes to things happening on your channel page (and be it because your channel page offers the UI controls for it, but other people's Fediverse frontends don't), this requires users to be detected as authenticated via OpenWebAuth single sign-on. So in this latter case, it means any user of Friendica, Hubzilla or (streams) and that one Forte user.
Anybody in this network: I'm not quite sure what this means. It's a setting from when only Hubzilla used the Zot protocol. So it may mean only authenticated Hubzilla users. But it may just as well mean only authenticated users of Hubzilla or (streams). It's probably meant to restrict certain things to only (potentially) nomadic users, but there never really has been any realistic use-case for this which is why (streams) doesn't have this option anymore.
Anybody on this website: Hubzilla channels on the same hub as yours. There are use-cases for this, but probably not on a personal channel.
Any connections: Anyone who is connected to you or tries to connect to you.
Approved connections: Only those whose connections requests you've granted, and who are fully connected to you.
Only those you specifically allow: This is where contact roles come into play.
Only me: Exactly this. No connection, no non-connection, only you yourself.

Here are my personal recommendations for settings:

Can view my channel stream and posts: Anybody on the internet
This defines both who is allowed to look at your channel with your posts in it on your home hub and whom you generally send your posts to. Choose [i]Anybody on the internet if you want people to see your channel stream or Anybody authenticated if you don't want people to see your channel stream (e.g. because you've come over from Friendica where you've kept the contents of your account secret).
Unless you really have a reason to keep your posts secret, choose Anybody on the internet. This makes you more interesting to aspiring followers and helps increase your reach.
Can send me their channel stream and posts: Only those you specifically allow
This defines who is allowed to send you their posts. The most elegant way of defining this is with Only those who you specifically allow and then by using contact roles to grant that permission to your contacts individually. That way, you can keep certain contacts who have connected to you first from flooding your stream with cruft.
Can view my default channel profile: Anybody on the internet
Unless you really have a reason for the general public to not see any of your profiles (you can optionally have multiple ones; we'll get to that), don't restrict this. Again, people are more likely to follow you, thereby increasing your reach, if they know who that is whom they may or may not follow.
Can view my connections: Anybody on the internet
Basically similar to Can view my default channel profile. You can't define different sets of connections visible to individual users, but what you can do is hide certain connections.
Can view my file storage and photos: Anybody on the internet
You really should not choose any other permission level than this. This also defines who can see pictures that you've embedded in your posts. If you limit this, certain people won't be able to see the pictures in your posts. For certain files that you don't want to embed in posts, you can always define individual custom access permissions.
That is, if you absolutely, positively have to restrict this, you'll also have to switch on Enable OCAP access in the privacy settings.
Can upload/modify my file storage and photos: Only me or Only those you specifically allow
You don't want the wrong people to mess with your files, now, do you?
Can view my channel webpages: Anybody on the internet
This does not refer to your channel page, by the way. It's about the Webpages app which allows you to have simple static webpages on your channel. And in most cases, such webpages are to be seen by the general public. (By the way: Even the official Hubzilla website is actually a Hubzilla channel.)
Can view my wiki pages: Anybody on the internet
In case you didn't know: You can have wikis on your Hubzilla channel. Multiple ones per channel with multiple pages each. In general, they're the most useful as general information sources, but you can always restrict access to them by assigning them to privacy groups.
Can create/edit my channel webpages: Only me or Only those you specifically allow
Can write to my wiki pages: Only me or Only those you specifically allow
Only those who you specifically allow is useful if you want to appoint collaborators for your webpages or wikis. Still, these collaborators can't delete webpages or wiki pages, only you can.
Can post on my channel (wall) page: Choose as you see fit
This actually doesn't really matter. It's another OpenWebAuth thing: Friendica, Hubzilla and (streams) users and that one Forte user theoretically can load your channel page in their browser and directly post to you on it. Since this is limited to those whom Hubzilla recognises as logged in via OpenWebAuth, it isn't like countless Mastodon users can spam your wall. And Anybody on the internet is not available as an option for obvious reasons.
Can comment on or like my posts: Anybody authenticated
This is how the rest of the Fediverse works. This is the only option which the vast majority of the Fediverse expects. Anything more restrictive would only irritate it and not even work properly in conjunction with places in the Fediverse like Mastodon that neither have nor know permissions. And Anybody on the internet is only an invitation to spambots. Trust me, they've already found Hubzilla.
Can send me direct messages: Anybody authenticated
Again, this is how the rest of the Fediverse works and what it expects. You'd need very good reasons to restrict this further. And if you restrict this further, users of Mastodon etc. will still be able to send you DMs, but they'll never know that their DMs have never reached you.
Can like/dislike profiles and profile things: Anybody authenticated
Another OpenWebAuth thing, so this will only affect very very few users.
Can chat with me: Choose as you see fit
The chat is another optional app, it's off by default, it isn't available on all hubs, and it's only other Hubzilla users whom you could chat with anyway if you installed the Chat app. So it doesn't really matter.
Can source/mirror my public posts in derived channels: Anybody authenticated
This sounds alarming, like who is allowed to clone your channel. But nobody is allowed to clone your channel but you.
What this really is about is who is allowed to repeat (= repost, retweet, boost, renote) or share (= quote-tweet, quote-post) your posts. But this permission only works within Hubzilla, (streams), Forte and maybe Friendica. It can't keep Mastodon users from boosting your posts anyway, just like Mastodon's planned quote-post opt-in or opt-out most likely can't keep Hubzilla users from sharing Mastodon toots.
Can administer my channel: Only me
For a personal channel, nothing else makes sense. This is mostly for things like forum channels for which you want to appoint additional admins.
Group actor: No.
This switch turns your channel into a forum. But it isn't a forum, it's your personal channel.

Once you're done, simply close the dialogue. You don't have to confirm these settings.

2025-01-09 14:59:21

dynamic_hubzilla

dynamic@hub.netzgemeinde.eu

@Jupiter Rowland

This is a great resource, Jupiter. Thank you for posting it.

"'Public' is too lax and will get your stream flooded, once you have a few hundred Mastodon contacts."

I would actually argue that "Public" is *exactly* what most new users coming to Hubzilla without pre-existing Fedi contacts would be looking for. Get some traffic to interact with, start interacting, start making connections. If the problem turns into information overload, they can always worry about curation until later.

Tangentially, @David Palk, one general Fedi tip is that interacting with people is the best way of making connections. If you can find people with common interests and express some enthusiasm for their posts, that gives them a reason to check out your profile and see whether you're someone *they'd* like to connect with.

2025-01-09 15:12:58

Scott M. Stolz

scott@loves.tech

@Jupiter Rowland

"Public" is too lax and will get your stream flooded, once you have a few hundred Mastodon contacts. "Personal" is too restrictive in a way that can impossibly be patched up with contact roles. It'd be secure enough if the Hubzilla grid was an enclosed thing, but it's too limited for a Fediverse where Hubzilla is tiny.

I don't think public is too lax. After all, you don't have to follow anyone back.

Public just means everyone can see your posts.

You only get flooded with posts if you automatically follow everyone that follows you, which is a separate setting.

2025-01-09 15:13:19

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@dynamic_hubzilla

I would actually argue that "Public" is *exactly* what most new users coming to Hubzilla without pre-existing Fedi contacts would be looking for. Get some traffic to interact with, start interacting, start making connections. If the problem turns into information overload, they can always worry about curation until later.

It's easier right now, yes. But it'll cause headache later on.

I used to have this channel on Public, too. But the more Mastodon users started following me for that one smart post or comment they've read from me, the more of them started pumping their completely uninteresting posts and boosts into my stream.

Eventually, I reached a point at which I had some 300 contacts. Most of them were on Mastodon, most of them had followed me for one smart post or comment. On the other hand, I had to follow them all back to allow me to follow them. On the other hand, practically none of them ever posted anything interesting for me.

My stream was flooded by an utter deluge of posts and boosts, 99% of which were completely uninteresting cruft which I had to wade through to find that 1% that was interesting.

I tried filtering. Didn't work because I can't use whitelist filters with both multiple keywords and the restriction that only posts shall be filtered, not comments or DMs. Hubzilla can't do that. I ended up not receiving DMs because they didn't contain any of the keywords on my whitelist.

So I had to resort to permissions. I made contact roles that explicitly allow contacts to send me their posts, I made contact roles that don't allow contacts to send me their posts.

And then I had to go through over 300 contacts, one by one, and assign new contact roles to them.

Afterwards, I could set my channel role to Custom and remove the channel-wide permission to send me posts. And then the number of posts coming in became much more bearable.

By the way: (streams) doesn't have a Public "as much allowed as on Mastodon" role anymore. Its permissions system has become much easier to use. You don't even have to rely on contact roles anymore, they're just presets for your convenience while you can flick single permissions on and off for each of your contacts. There's no need anymore for a channel role that's conveniently lax at first glance, especially if it turns into inconveniently lax after a while.

2025-01-09 15:17:28

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@Scott M. Stolz

After all, you don't have to follow anyone back.

As far as I know, you do.

If someone wants to follow you, they can't follow you just like this. Not by default. Instead, you have to confirm the connection to give them permission to receive your posts. But by doing so, you establish a bidirectional, mutual connection which, depending on channel and contact roles, also permits them to send you their posts.

If you don't confirm the connection, they don't receive anything from you because they have no permission.

The only way to have a follower-only connection is by not permitting a contact to send you their posts both in the channel role and in the contact role assigned to that contact.

2025-01-09 15:22:46

Scott M. Stolz

scott@loves.tech

One thing to consider is that Hubzilla has two levels:

1. Connections (you follow them) = They can see both public and private posts. They do not even have to follow you back to see your posts.

2. Followers (they follow you but you don't follow them back) = They can only see your public posts.

This is not explained in the UI, but that is how it works.

2025-01-09 15:34:07

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@Scott M. Stolz That'd mean that if someone wants to follow me, I can simply delete the connection request, and they do follow me nonetheless. In this case, unless I manually kept track of connection requests, I wouldn't know just how many actors follow me because there's no list of followers.

Does that also mean that I can delete those confirmed connections that aren't allowed to send me posts, and they will still continue following me and be permitted to receive my posts?

Also, how does that tie into nomadic identity, especially moving a channel?

2025-01-09 15:44:02

Scott M. Stolz

scott@loves.tech

@Jupiter Rowland

As far as I know, you do.

That's the difference between a public and personal channel. Public channels can be followed even if you do not follow them back. Hubzilla supports one way connections. It just does not show it in the user interface.

I just tested it out. I created a brand new Hubzilla account called "Test Account" set to public. I followed it from this account. I posted on the test account. Even though the test account did not follow me back, I was notified of its public posts on this account.

People can still see your public posts, even if you do not connect with them.

2025-01-09 15:51:12

dynamic_hubzilla

dynamic@hub.netzgemeinde.eu

@Scott M. Stolz

"One thing to consider is that Hubzilla has two levels:

1. Connections (you follow them) = They can see both public and private posts. They do not even have to follow you back to see your posts.

2. Followers (they follow you but you don't follow them back) = They can only see your public posts.

This is not explained in the UI, but that is how it works."

Wait, is this true? I get why it would be true for Mastodon followers because Mastodon just doesn't have that many ways of understanding connections, but I would have assumed that for Hubzilla/Hubzilla contacts there wouldn't be any content sent out if there wasn't a connection.

I've set up a "Followers" role for my channel specifically so that I can let people follow me without needing to follow them back. I'm now wondering if this is necessarily the right approach.

2025-01-09 15:58:13

Scott M. Stolz

scott@loves.tech

@dynamic_hubzilla Yes, it is true.

And I just tested it with a Test Account set to personal. I connected to it (followed it) from this account. It did not follow me back. I get notified of its public posts, but not its private posts.

People can follow your public posts, even if you don't follow them back (connect with them).

2025-01-09 16:03:00

dynamic_hubzilla

dynamic@hub.netzgemeinde.eu

@Scott M. Stolz

Thanks.

How did you handle the new connection notification?

2025-01-09 16:27:42

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@dynamic_hubzilla In theory, you should simply be able to delete it without confirming it. The contact would follow you, and it wouldn't be any of your business because they'd see what's public anyway.

What's more interesting, however, is what'd happen if someone asked to connect, you confirmed, and then you deleted the confirmed connection. Would it be demoted to follow-only or completely disrupted? If the former, I can weed out my connections dramatically.

2025-01-09 16:35:42

Scott M. Stolz

scott@loves.tech

Here is how Hubzilla connections (followers) work:

1. Mutual Connection: You connect with them / they connect with you.

- Notifications:
   - You are notified of their posts
   - They are notified about yours.
- Public Posts:
   - Both of you can see each others public posts.
- Private Posts:
   - Both of you can see each others private posts.

2. Follower: They connect to you / you do NOT connect with them.

- Notifications:
   - They are notified of your public posts, but not your private posts.
   - You are not notified about any of theirs.
- Public Posts:
   - Both of you can see each others public posts.
- Private Posts:
   - You can see their private posts, but they cannot see yours.

3. Follow: You connect to them / they do NOT connect with you.

- Notifications:
   - You are notified of their public posts, but not their private posts.
   - They are not notified about any of yours.
- Public Posts:
   - Both of you can see each others public posts.
- Private Posts:
   - They can see your private posts, but you cannot see theirs.

Note:

If they don't connect with you, they won't get notifications. However, they can still see your public posts, either by visiting your channel, seeing a repeat of your post, or reading your comment on someone else's post. If you connect with them, they can still see your private posts by visiting your channel while logged in with OpenWebAuth even if they don't connect back.

2025-01-09 16:40:00

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@Scott M. Stolz So if I deleted a mutual connection initiated by the other side, it would be demoted to a follower connection and not fully disconnected?

2025-01-09 16:43:13

Scott M. Stolz

scott@loves.tech

@Jupiter Rowland ~~Yes.~~ Disconnecting is not a block. They can still see your public posts. They would lose access to all of your private posts though.

I am not sure if your hub would still send notifications to them, but I am pretty sure it would continue to do so.

I have not tested this.

2025-01-09 16:49:00

Scott M. Stolz

scott@loves.tech

You can see people who follow you by going to:

/connections/followers

2025-01-09 16:59:53

Scott M. Stolz

scott@loves.tech

@Jupiter Rowland I just performed a test.

If you delete a follower (connection), it does remove them as a follower and they are no longer notified about your posts.

However, this is not a block, and they can still see and interact with your public posts. Deleting a connection only affects notifications.

Also, they can simply follow you back again since they are not blocked.

2025-01-09 17:32:02

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@Scott M. Stolz Then it's not a problem. I'm generally talking about Mastodon followers. They only expect my public posts to wash up on their timelines with no notification, and I never post to generic followers in private anyway.

2025-01-09 17:49:19

Scott M. Stolz

scott@loves.tech

@Jupiter Rowland I have not tested any of this with ActivityPub. I only tested Hubzilla / Hubzilla connections. But if you remove a connection, Hubzilla wouldn't know to send a notification, so the same rules should apply with ActivityPub and Mastodon.

2025-01-09 19:12:47

dynamic_hubzilla

dynamic@hub.netzgemeinde.eu

@Scott M. Stolz

"You can see people who follow you by going to:

https://hub.netzgemeinde.eu/connections/followers"

When I follow that link, the list I see includes RSS feeds that I subscribe to, complete with the big red "Accepts: Nothing" dot. It seems misleading to refer to this list as "Followers."

2025-01-09 19:25:08

dynamic_hubzilla

dynamic@hub.netzgemeinde.eu

@Scott M. Stolz

"If you have your channel set to "personal" then only your connections can see your posts. Your posts are not public. This limits who can see and interact with your channel."

Coming back to this because it's bothering me.

What does it mean to set a post's privacy level to "Public" on a channel that is set to "Personal"?

I currently have my channel set to "Personal", and I'm wondering if that was a mistake. But I'm also apprehensive about what would change about my experience if I now switched the channel to "Public".

It isn't at all clear to me how channel roles interact with the privacy level of posts.

2025-01-09 20:28:24

David Palk

palky@hub.netzgemeinde.eu

@dynamic_hubzilla thanks buddy that was really useful.
Idiot question, if I click edit and 'approve' but it still shows 'pending approval' does that mean the other party hasn't seen the 'contact request'?

2025-01-09 20:34:24

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@David Palk No, it means that Netzgemeinde tends to be a little slow at this. Wait a little, and it goes away.

2025-01-10 01:46:09

Scott M. Stolz

scott@loves.tech

@dynamic_hubzilla The biggest thing is that it would change the default status of all future posts. But the permissions of all of your previous posts will stay the same.

Every post that is "friends only" will stay "friends only" even if you change your channel to "public."

Public =When you create a post, it assumes that you want it "public" unless you change the settings of that individual post.

Personal = When you create a post, it assumes that you want it "friends only" unless you change the settings of that individual post.

Remember, you can always change the permissions on a post-by-post basis, regardless of which channel type you have.

2025-01-10 13:22:05

dynamic_hubzilla

dynamic@hub.netzgemeinde.eu

@Scott M. Stolz

Ok, that is a relief. From some of the things that people said in this thread, I'd begun to wonder if the channel's role actually did something separate from changing default post settings.

2025-01-10 15:43:21

Scott M. Stolz

scott@loves.tech

@dynamic_hubzilla The biggest thing is that you have to remember what the default setting is, otherwise you can accidentally create a post with the wrong permissions.

For people who regularly post "friends only" posts, I would keep the setting to "personal" and manually change public posts to "public." But if you are like me, and almost everything you post is public, then the "public" setting makes more sense.

2025-01-10 17:16:39

dynamic_hubzilla

dynamic@hub.netzgemeinde.eu

@Scott M. Stolz

Because I use Privacy Groups, I kind of have to be alert to the possibility of posting to the wrong privacy level anyway. And it's a lot easier to mitigate the harm if I accidentally make a locked posted when I meant for it to be Public than the other way around.

Like you, most of my posts are public, but for me I still think it makes sense to leave my channel role as "Personal".