Feature Request: Filter comments for # to not publish on blog

[jaschaurbach]

I read some discussions and thought about how to avoid people getting angry that their answer to a post is getting federated onto the blog as well. I know, federation is about having all the things decentralized and saved on many places but people, we all knot the problem :D

I came up with an idea: how about to define a # when used in a comment (like #noblog), this comment will not be considered as an answer to the post and will never show up as a comment. A Bonus would be that these comments will be shown on to logged in admins and authors of the post somewhere under the article or on a new page.

Let me know what you think., I am of course open to discussion and will not be mad if this is not considered as I know the try proposal is going against the idea of federation in the Fediverse.

[mediaformat]

This is an important issue! I think we have to balance broad user expectations with actual user behaviour.

(Mastodon) Users can choose not to have their own profiles / status indexed, but with public / unlisted replies going to other servers there are no guarantees or expectations.

And partial indexing is not really a thing, at best we could exclude received comments that are Unlisted (Don't show up in the federated timelines), adding the data-nosnippet-attr. But the content is still technically indexed by Google, just doesn't show up in snippets.

The other possibility would be to accept Follower-only and Direct messages in reply to our posts, despite not currently supporting replying with the same visibility.

[jaschaurbach]

I admit, I created this request after I encountered a discussion which I do to find any more to link to it. It was about that people were not happy that their content "leaves the Fediverse" (woah) and are stored on an another website without their consent.

I think it Is a cultural problem here that many users think Fedivers == Mastodon/Pleroma/Misskey but not a "private Website" of someone else. I thought about the easiest way to deal with it and it was "just do not show answers with a predefined hashtag"

[maste9]

I can offer a current thread (in german) corresponding to this topic:

https://mastodon.social/@monoxyd/109310497402246212

At least it touches the same privacy problem.

Of course we know that no info in the fediverse is actually private. But there's certainly a difference between s.o. searching for my "protected" content on purpose and publishing protected toots/posts as public. I find it quite understandable that people don't want their stuff to appear anywhere else when they choose to publish it as "Followers only" or "Unlisted" ...

So I would propose that only posts marked as public should be displayed in the comments. So every object that isn't "sensitive: false" should be excluded from being processed, right?

I guess there would still be users complaining about that, because they don't know, that their public posts are ... yeah ... public ... But I could live with that as long as I could tell them that they can easily "protect" their remarks.

Sorry that I can't express that in concrete code :sweat_smile: I'm not advanced enough for that.

[timnolte]

Would it be possible to still create comments in WordPress that are not public, in the cases where replies in the Fediverse were not marked public? I ask this as I understand people not wanting their replies posted public on my site but I still want then captured on my site so that I can have them available when logged into the WordPress dashboard.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[pfefferle]

Keep

[github-actions[bot]]

This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions[bot]]

This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 5 days.